Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

graph_paginate

Fetch all data items from a GET endpoint by automatically handling pagination, with a configurable page limit to prevent runaway requests.

Instructions

Auto-paginate a GET endpoint and return a flat list of all data items.

Stops at max_pages to prevent runaway calls.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "graph_paginate"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
endpointYes
max_pagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses two behavioral traits: it returns a flat list of all data items, and it stops at max_pages to prevent runaway calls. Since there are no annotations, these are useful but incomplete; it doesn't mention that it makes multiple HTTP calls or how errors are handled.

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?

Two concise sentences, the first stating the core purpose and the second providing a safety guarantee. No extraneous information; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description is too sparse. It doesn't describe the shape of the returned items, how pagination is handled beyond max_pages, error behavior, authentication requirements, or potential side effects like multiple network calls. This is insufficient for a generic utility.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description gives no explanation of the 'params' parameter, which is an optional object for query parameters. It only indirectly mentions max_pages (as a limit) and 'endpoint' (as GET endpoint). With 0% schema description coverage, this leaves a significant gap in parameter understanding.

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?

The description opens with 'Auto-paginate a GET endpoint' which clearly identifies the verb (auto-paginate), resource (GET endpoint), and output (flat list of all data items). This distinguishes it from siblings like graph_call which likely returns a single response.

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?

The phrase 'GET endpoint' implies this tool is for paginated GET requests, providing clear context for when to use it. However, it doesn't explicitly state alternatives or when not to use it (e.g., for POST endpoints).

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

Deploy Server

Other Tools