Skip to main content
Glama

Ad campaign details

get_ad_campaign_details
Read-onlyIdempotent

One ad campaign with pacing, spend, ROAS and current state.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_ad_campaign_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesThe ad campaign id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the result carries pacing, spend, ROAS and 'current state', which is useful context absent from any output schema, but 'current state' is left undefined (status enum? active/paused?) and nothing is said about behavior for an unknown or inaccessible campaign_id.

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?

A single tight fragment with no filler, and the most important information (single campaign, key metrics) comes first. It is lean to the point of being a fragment rather than a sentence, but nothing is wasted or buried.

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

Completeness3/5

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

For a one-parameter, annotation-covered read tool this is close to sufficient, and the field list compensates for the missing output schema. Still, the undefined 'current state' and the absence of any error or not-found behavior leave a small but real gap for an agent calling it blind.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage ('The ad campaign id'), so the schema already does the work and the baseline is 3. The description adds no meaning about where a campaign_id comes from or what format it takes.

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

Purpose3/5

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

The noun phrase 'One ad campaign with pacing, spend, ROAS and current state' makes the resource and the singular scope clear, and the field list hints at a fetch of a single campaign. But there is no verb, so the agent must infer retrieval rather than being told, and no sibling (e.g. get_ads_overview, get_planner_campaign) is named to confirm this is the single-campaign lookup.

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

Usage Guidelines2/5

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

No when-to-use guidance at all: nothing says to use this for a known campaign_id versus a listing or overview tool, and there are no prerequisites or exclusions. The agent must derive usage purely from the name and the single required id.

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