Skip to main content
Legacy API: prefer sessionsThis guide covers legacy direct-execution methods, which remain supported for existing integrations. For new integrations, use sessions to discover and fetch tools at runtime. If you need a fixed tool set, consider the direct tools preset. See Sessions vs direct execution and the migration guide.
Fetch specific tools, filter by permissions or search, and inspect schemas for type information. Tools are automatically formatted for your provider. Not sure which toolkit covers your use case? Browse the Toolkits catalog — each toolkit page lists its tool slugs — or search by task below.

Basic usage

Returns up to 20 tools by default. Tools require a user_id because they’re scoped to authenticated accounts. See User scoping and Authentication.

Tool schemas

Inspect tool parameters and types without a user_id:
Generate type-safe code for direct SDK execution with composio generate. This creates TypeScript or Python types from tool schemas.
View tool parameters and schemas visually in the Composio platform. Navigate to any toolkit and select a tool to see its input/output parameters.

Filtering tools

By toolkit

Get tools from specific apps. Returns up to 20 tools by default. limit caps the number of returned tools. It does not select the tools needed for a task or guarantee relevance order. A small limit can exclude the tool you need. For a fixed workflow, fetch explicit tool names.
TypeScript: limit and important toolsWhen you filter only by toolkit, the TypeScript SDK automatically requests tools marked important unless you set important: false. Supplying limit, search, or tags disables that automatic filter. To keep the important subset with a limit, pass important: true explicitly. The Python SDK does not expose this option.

By name

Fetch specific tools when you know their names.

By scopes

Filter OAuth tools by permission level. Only works with a single toolkit.

By search (experimental)

Search for tools with the search option. Start with short action keywords such as create event, free busy, or send email, and narrow the query with toolkits when you know the app. Inspect the returned descriptions and input schemas before selecting a tool. Do not assume the first result is the best match or that a natural-language goal returns every relevant tool. If you get no results, shorten the query or fetch a known tool by name.
These SDK examples use latest by default. REST v3 tool endpoints default to 00000000_00; REST v3.1 tool endpoints default to latest. Pin a dated version when application code parses tool output. See toolkit versioning.

Next

Executing tools