Skip to main content
Glama

list_integrations

Read-onlyIdempotent

List registered native integrations for this workspace. Unscoped calls return id, name, and operationIds; pass ids or query (for example { ids: ["zendesk"] }) for operation descriptions plus requestSchema/responseSchema. Use when wiring a playbook to a vendor (CRM, helpdesk, email) so step code can call metaphor.integration instead of inventing a custom HTTP tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoExact integration ids, e.g. ["zendesk"]. Combined with query via OR.
queryNoCase-insensitive match on integration or operation id/name/description
includeOperationsNoInclude operation descriptions. Default false when unscoped; default true when ids or query is set.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent), so the description's added value is the response-shape variation: unscoped calls yield id/name/operationIds, while scoped calls yield operation descriptions plus requestSchema/responseSchema. That is genuinely useful behavioral detail an agent cannot infer from the annotations. It does not mention pagination, limits, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the purpose, then the return-shape rule, then the usage trigger. The inline example earns its place by making the ids argument concrete, and there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly takes on the burden of explaining what comes back at each scope level, which is the most important gap it could fill. It leaves out pagination, result limits, and any permission prerequisites, which are minor for a read-only list tool but still absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning by tying parameter usage to outcome: passing ids or query changes what fields come back, illustrated with a concrete payload {" ids: ["zendesk"] }. It largely echoes the schema's includeOperations default rather than expanding on it, which keeps it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus scope: "List registered native integrations for this workspace." The reader knows exactly the object being enumerated. It stops short of explicitly distinguishing itself from nearby siblings like list_tools or list_mcp_tools, so it is clear but not sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage context: "Use when wiring a playbook to a vendor (CRM, helpdesk, email) so step code can call metaphor.integration instead of inventing a custom HTTP tool." That names the situation and the anti-pattern it replaces. It does not name a specific alternative tool to prefer in other situations, so no explicit when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources