AdCopilot

Google Ads: look up report fields

get_resource_metadata

Read-onlyIdempotent

Retrieves the selectable, filterable, and sortable fields for a specific Google Ads resource.

Use this tool to find out which fields you can select, filter by, or sort by
when querying a specific resource (e.g., 'campaign', 'ad_group').
Do not guess fields, you MUST use this tool to discover them.

The responses of this tool should be cached, as they don't change frequently.

A name that is not a resource has no fields; the answer then carries a
note and valid_resources, the resource names the search tool accepts.

Args:
    resource_name: The name of the Google Ads resource (e.g., 'campaign', 'ad_group').

Tools revision: d80f65c0.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource_name": "<resource_name>"
    },
    "name": "get_resource_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`resource_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the burden is lighter, and the description still adds real behavior: results are stable enough to cache, and an invalid resource name returns a note plus a valid_resources list rather than an error. It omits auth or rate-limit context, but that is minor for a read-only metadata lookup.

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

Conciseness4/5

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

Front-loaded with the purpose, then usage rules, then edge-case behavior — a sensible order. The trailing 'Args: resource_name' line largely restates the opening sentences and the schema, so there is one redundant block, but the rest is dense with useful guidance.

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 one-parameter, read-only discovery tool with an output schema and full annotation coverage, everything an agent needs is present: purpose, mandatory usage, caching posture, and the failure path with valid_resources. No return-value explanation is needed since the output schema covers it.

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 description coverage is 0%, so the description carries the parameter alone — and it does, naming resource_name's meaning and giving two concrete example values ('campaign', 'ad_group'). The invalid-name behavior further clarifies what the accepted value space is, though it never states the accepted format explicitly.

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?

States a specific verb and resource: retrieves the selectable, filterable, and sortable fields for a specific Google Ads resource. The second sentence clarifies this is a pre-query discovery step, which distinguishes it from the sibling 'search' tool that actually runs queries.

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?

Explicit when-to-use (before selecting/filtering/sorting on a resource), a hard prohibition ('Do not guess fields, you MUST use this tool'), a caching instruction so the agent does not re-call redundantly, and a pointer that the search tool is what consumes valid_resources. That covers use, non-use, and the alternative in one place.

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

All AdCopilot 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?