Skip to main content
Glama

brand_changes

Watch a competitor: what changed for one brand since a date. Use it for 'what's new from ', 'did they launch or stop ads', 'what is scaling for them this week'. Returns, each with its date and source: ads started (Meta's start date), ads stopped (Meta's stop date), ads whose version count rose, new ads relaunching a media the brand already used, and the ads whose EU reach grew most between two readings. Get the page_id with find_brand. Costs 5 credits (0 if nothing changed).

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": {
      "page_id": "<page_id>"
    },
    "name": "brand_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNodefault: 7 days ago
page_idYesMeta page id (from find_brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost (5 credits, waived when nothing changed) and enumerates exactly what counts as a change, including the underlying Meta start/stop dates. It does not state read-only safety explicitly, but 'watch' and the absence of any mutation language make that unambiguous.

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 the selecting use cases, then the return inventory, then the operational notes (page_id source, cost). The return enumeration is long but each category is distinct and actionable; the only mild clutter is 'between two readings', which is left undefined.

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?

There is no output schema, so the description correctly enumerates return categories with dates and sources, and it covers cost and the required identifier's origin. It leaves open the relationship to watchlist_changes and whether results are bounded or paginated, which matters for a change-feed tool.

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?

Schema coverage is 100%, so both parameters are already documented, including the 'default: 7 days ago' for since. The description adds one useful link — that page_id comes from find_brand — but nothing about date format or the semantics of the comparison window beyond what the schema states.

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 ('what changed for one brand since a date') plus the scope qualifier 'one brand', which implicitly separates it from the watchlist-level sibling. An agent can tell this is a per-brand change-detection tool without opening the schema.

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 concrete user phrasings that select this tool ('what's new from <brand>', 'did they launch or stop ads', 'what is scaling for them this week') and routes the agent to find_brand for the required page_id. It stops short of naming watchlist_changes as the alternative for multi-brand monitoring, so the exclusion is left to inference.

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