list_provider_tools
Lists every tool a client's provider account exposes, including name, description, argument schema, and read-only status. Filter by keyword or schema to find the right tool before invoking it.
Instructions
What this client's account with this provider can actually be asked to do.
Every provider here runs its own MCP server with its own tools, and
this returns them: the name, what it does, its argument schema, and
whether the provider marks it read-only. Pair it with
call_provider_tool, which invokes one.
This is how you do work Munim has no verb for. There is no per-operation
tool to look for, because modelling one provider's tools as another
tool's parameters is a losing game: Cloudflare's execute takes
JavaScript. Read this list, then call what it names.
read_only is what the provider says about its own tool, and null means
it said nothing. It is reported, not enforced; naming a client is what
unlocks writing (D5).
names_only returns the name and read_only and nothing else, which
for Resend is 2KB against 122KB. Use it first: the full listing has
exceeded a caller's response limit outright. matching filters on the
name, the description and the argument schema, so "which tools take
a teamId" is answerable, which it is not by name and description alone.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client | Yes | The client to act on, by the name you registered them under. A write resolves this one client's credentials and no other. | |
| matching | No | Only tools whose name, description or argument schema contains this. Searching the schema is how you find every tool that takes a teamId. | |
| provider | Yes | The provider to use, for example cloudflare, vercel or resend. Only what this client is actually connected to is reachable. | |
| names_only | No | Return names and read-only flags only. Resend publishes 121KB of schemas and 2KB of names. |