StealAds

Get a Playbook

get_playbook

Read-onlyIdempotent

Returns the latest Playbook for one competitor of one brand: a written summary of that competitor's ads with ideas to try against them. Read-only and spends nothing. When none has been created the result is Playbook not found; create_playbook builds one.

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": {
      "brand_id": "<brand_id>",
      "competitor_id": "<competitor_id>"
    },
    "name": "get_playbook"
  }
}

Input Schema

Name	Required	Description
`brand_id`	Yes	Brand id from list_brands.
`competitor_id`	Yes	Competitor id from list_competitors.
`response_format`	No	Output format: text (default) or json. table is not available for this tool.

Output Schema

Name	Required	Description
`hero`	No	hero value in this response.
`kept`	No	kept value in this response.
`wall`	No	wall value in this response.
`scope`	No	Which accessible ad examples this search covered.
`asOfMs`	No	asOfMs value in this response.
`counts`	No	counts value in this response.
`brandId`	No	brandId value in this response.
`formats`	No	formats value in this response.
`retired`	No	retired value in this response.
`testing`	No	testing value in this response.
`survival`	No	survival value in this response.
`creatives`	No	creatives value in this response.
`graveyard`	No	graveyard value in this response.
`competitor`	No	competitor value in this response.
`formatFacts`	No	formatFacts value in this response.
`campaignSeed`	No	campaignSeed value in this response.
`changedSinceRead`	No	changedSinceRead value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / response_format / description

Previous value: -"Output format: text or json for capped research examples; table is available only for tracked rival rows."New value: +"Output format: text (default) or json. table is not available for this tool."

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: that the call spends nothing, that only the latest version is returned, and the exact 'Playbook not found' shape when nothing has been created.

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 short sentences, front-loaded with purpose then behavior then the failure case and alternative. Every clause carries information an agent would otherwise have to discover by trial.

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 an output schema present, return-value detail is unnecessary, and the description covers cost, scope, staleness ('latest') and the empty case. Minor gap: it does not say whether a Playbook can become stale relative to newly ingested ads.

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 brand_id, competitor_id and response_format are already fully documented including enum restrictions. The description reinforces the one-competitor-of-one-brand constraint but adds no format or sourcing detail beyond the schema, so the baseline 3 applies.

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 (returns the latest Playbook), scopes it precisely to one competitor of one brand, and explains what a Playbook actually contains (a written summary of that competitor's ads with ideas to try against them). An agent can distinguish it from list_playbooks and create_playbook without opening any 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 clear context for retrieval and explicitly routes the agent to create_playbook when no Playbook exists yet, which is the main ambiguity an agent would face. It does not address when to prefer list_playbooks over a single fetch, so it stops short of full when/when-not coverage.

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

All StealAds 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.