Skip to main content
Glama

account_request_history

Recent API requests for your key — requestId, status, credits, cacheHit (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_request_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 50, max 500). Free — does not consume credits.
sinceNoInclusive lower bound on createdAt (ISO date or datetime).
untilNoExclusive upper bound on createdAt (ISO date or datetime).
cursorNoPagination cursor from nextCursor (createdAt of the last row). Leave empty for the first page.
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.
endpointNoExact Captapi path filter, e.g. /v1/instagram/basic-profile.
statusCodeNoFilter by HTTP status code (e.g. 500).

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. Changed6 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Pagination cursor from nextCursor (createdAt of the last row). Leave empty for the first page.",
      +  "type": "string"
      +}
    • changedInput schema / properties / endpoint / description
      Previous value: -"Exact Captapi path, e.g. /v1/instagram/basic-profile."New value: +"Exact Captapi path filter, e.g. /v1/instagram/basic-profile."
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows to return. Default 50, max 500. Free — does not consume credits."New value: +"Max rows to return (default 50, max 500). Free — does not consume credits."
    • changedInput schema / properties / since / description
      Previous value: -"Inclusive createdAt lower bound (ISO date or datetime)."New value: +"Inclusive lower bound on createdAt (ISO date or datetime)."
    • changedInput schema / properties / statusCode / description
      Previous value: -"HTTP status filter, e.g. 500."New value: +"Filter by HTTP status code (e.g. 500)."
    • changedInput schema / properties / until / description
      Previous value: -"Exclusive createdAt upper bound (ISO date or datetime)."New value: +"Exclusive upper bound on createdAt (ISO date or datetime)."
  4. Changed5 schema fields changed
    • addedInput schema / properties / endpoint
      Added value: +{
      +  "description": "Exact Captapi path, e.g. /v1/instagram/basic-profile.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 50, max 500. Billed per result."New value: +"Max rows to return. Default 50, max 500. Free — does not consume credits."
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Inclusive createdAt lower bound (ISO date or datetime).",
      +  "type": "string"
      +}
    • addedInput schema / properties / statusCode
      Added value: +{
      +  "description": "HTTP status filter, e.g. 500.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / until
      Added value: +{
      +  "description": "Exclusive createdAt upper bound (ISO date or datetime).",
      +  "type": "string"
      +}
  5. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job on the economic behavior: it discloses that the call costs 0 credits, that empty results and failures are never charged, and that a cache hit returns 0 credits with a 24h caching window defaulting to fresh. It omits auth expectations, rate limits, and the response envelope/pagination contract (nextCursor), which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the resource and its returned fields, then moves to cost and caching. The cost message is repeated three times in close succession ('credits', 'Costs 0 credits', 'never charged'), which is mildly redundant but not wasteful enough to hurt.

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?

For an 8-parameter, zero-required read tool with no output schema and no annotations, the definition covers the two things the schema cannot: pricing semantics and caching behavior, which are the main decision factors. It is slightly incomplete in not explaining what the response envelope looks like or how nextCursor is surfaced, and it references a 'cache' parameter the schema does not define.

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 description coverage is 100%, so the schema already documents every parameter and the baseline of 3 applies. The only parameter-level meaning the description adds is for 'cache=true' — but no such parameter exists in the schema, and additionalProperties is false, so that guidance is unusable and slightly misleading rather than value-adding.

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+resource ('Recent API requests for your key') and enumerates the payload fields returned (requestId, status, credits, cacheHit), which distinguishes it from aggregate siblings like account_daily_usage or account_most_used_routes. It does not explicitly name an alternative, so it stops short of a 5.

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?

Useful operational guidance is present in the form of 'Pass cache=true for a free 24h cache hit (default always fresh)' and the zero-cost framing, which implies this is the cheap way to inspect traffic. However, there is no explicit when-to-use-this-vs-another-tool statement (e.g. versus account_daily_usage for aggregates), so routing is only implied.

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.