Skip to main content
Glama

account_most_used_routes

Ranked list of which Captapi routes your key calls most (0 credits). Costs 0 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to include (default 30, max 365).
limitNoMax rows to return (default 20, max 100). Free — does not consume credits.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Number of days to include. Default 30, max 365."New value: +"Number of days to include (default 30, max 365)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows to return. Default 20, max 100. Free — does not consume credits."New value: +"Max rows to return (default 20, max 100). Free — does not consume credits."
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 100. Billed per result."New value: +"Max rows to return. Default 20, max 100. Free — does not consume credits."
  5. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose valuable behavior: zero credit cost, no charge on empty results or failures, and fresh-by-default vs 24h cache semantics. Missing are the read-only nature, auth/scope requirements, and what a ranked row actually contains.

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 ranking purpose and kept to three clauses, and the cost information is placed where an agent will see it first. However, zero-credit pricing is stated twice ('0 credits' and 'Costs 0 credits') and the sentence about failures being uncharged partly repeats it.

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?

No output schema exists, so the description must convey the return shape, and 'ranked list of routes' is thin — no mention of the ranking metric, row fields, or sort order. It is complete on the billing/caching dimension but incomplete on what the agent will actually receive.

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 the schema already documents days, limit, fields and compact — the description adds nothing to those. Worse, it introduces a 'cache' argument that does not appear in the schema, which can mislead an agent assembling arguments. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: a ranked list of Captapi routes the key calls most, scoped to 'your key'. It is distinguishable from balance/usage siblings by the 'ranked routes' framing, though it never names account_request_history or account_daily_usage to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is only implied — an agent infers it is for cost/endpoint-popularity insight. There is a concrete operational hint (pass cache=true for a free 24h cache hit), but no when-to-use versus when-to-pick-a-sibling statement and no prerequisite or exclusion notes.

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.