Metadata MCP Connector

Show what Metadata can do

get_metadata_capabilities

Read-onlyIdempotent

Show an interactive, business-level overview of what this Metadata connection can do for the user: planning and launching campaigns, reaching target accounts, creating ads, managing spend, measuring impact and connecting their stack, with example requests to try. Its discovery part is the account's feature adoption per area and a few features worth trying next, the same report discover_features gives without the per-feature list, read from the account this connection is working in. Call it when the user has just connected Metadata, asks what Metadata or this connector can do, or asks for help getting started. Changes nothing; it only shows what this user's permissions and the account's plan allow. A pick with status needs_connection needs that connection first. A pick with basis mcp is unused only through Metadata's MCP connectors, so never tell the user they have not used it in the Metadata app. why_for_you is specific to this account only when personal is true. Give adoption per area as in_use out of measured, the features whose use can be proved or ruled out.

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": "get_metadata_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real context beyond them: results are bounded by 'this user's permissions and the account's plan,' and it warns that a needs_connection pick requires connecting first, that basis=mcp means unused only via Metadata's MCP connectors (so the agent must not claim non-use in the app), and that why_for_you is account-specific only when personal is true. These are exactly the traps an agent would otherwise fall into.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is a single dense run-on paragraph mixing usage triggers, sibling comparison, safety notes, and output-field semantics. Some sentences are grammatically strained ('Give adoption per area as in_use out of measured, the features whose use can be proved or ruled out'), and field-level detail is partly redundant with the output schema.

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

Completeness5/5

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

For a zero-parameter discovery tool, it covers everything an agent needs: when to call it, what it returns at a business level, permission/plan scoping, and the two edge cases (needs_connection, basis=mcp) that would otherwise produce wrong answers to the user.

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?

The tool takes zero parameters, so per the rubric the baseline is 4; there is nothing for the description to disambiguate. It does explain output-field semantics (in_use out of measured, basis, status, personal), which is a bonus even though an output schema exists.

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

Purpose5/5

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

Opens with a specific verb and resource ('Show an interactive, business-level overview of what this Metadata connection can do') and enumerates the concrete capability areas covered. It also explicitly distinguishes itself from the sibling discover_features, noting it is 'the same report discover_features gives without the per-feature list'.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions: after the user just connected Metadata, when they ask what Metadata or this connector can do, or when they ask for help getting started. It also names the nearest alternative (discover_features) and states the delta, so an agent can route correctly without inference.

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

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?