Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

List brands

list_brands
Read-onlyIdempotent

Lists the brands this account can use, most recently updated first, as short summaries with the brand id that other tools take as brand_id. Returns 25 per page by default (at most 50), with next_cursor when more exist. get_brand returns one brand's full details.

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

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor from the previous list_brands page; absent for the first page.
max_resultsNoBrands per page, 1 to 50 (default 25).
response_formatNoOutput format: text (default) or json. table is not available for this tool.

Output Schema

NameRequiredDescriptionDefault
brandsNoShort summaries of brands you can access.
has_moreNoWhether another bounded page is available with next_cursor.
next_cursorNoContinuation handle for the same filters; null when no further page is offered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Continuation handle from the same tool and filters; absent for the first page."New value: +"next_cursor from the previous list_brands page; absent for the first page."
    • changedInput schema / properties / max_results / description
      Previous value: -"Maximum number of results in this bounded response; constrained by the field maximum."New value: +"Brands per page, 1 to 50 (default 25)."
    • 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."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds pagination mechanics beyond that: 25 per page default, hard cap of 50, and next_cursor presence indicating more results. It stops short of describing summary fields or failure modes, so not a 5.

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 tight sentences: purpose and ordering first, pagination limits second, deferral to the sibling last. No filler and no repetition of annotation-level facts.

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?

Given an output schema and full annotation coverage, the description supplies exactly the missing pieces an agent needs: ordering, page sizing, cursor continuation, and the identifier handoff to other tools. Nothing required to call it correctly is absent.

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 coverage is 100%, so all three parameters are already documented. The description adds cross-parameter meaning by tying next_cursor to a prior page and explaining that the returned brand_id is what other tools accept, which is not obvious from the schema alone.

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 ('Lists the brands this account can use'), plus ordering ('most recently updated first') and result shape ('short summaries with the brand id'). An agent can distinguish this from sibling list_* tools and from get_brand purely from the text.

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?

Explicitly routes detail-seeking callers to get_brand ('get_brand returns one brand's full details'), which establishes when not to use this tool. It does not discuss other sibling list tools, but names alone do not establish that they overlap, so no exclusion is clearly owed.

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

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