Skip to main content
Glama

get_budget_pacing

Check campaign budget pacing to view hourly consumption, time out of budget, and pacing alerts for Amazon ad campaigns.

Instructions

Read campaign budget pacing: budget consumed by hour, time-out-of-budget percentage, and pacing alerts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:59-64 (registration)
    Tool registration for 'get_budget_pacing' in the tools array. Defines name, description, and inputSchema (empty object, no required parameters).
    {
      name: "get_budget_pacing",
      description:
        "Read campaign budget pacing: budget consumed by hour, time-out-of-budget percentage, and pacing alerts.",
      inputSchema: { type: "object", properties: {}, additionalProperties: false },
    },
  • The CallToolRequestSchema handler. Since there is no specific case for 'get_budget_pacing', it falls through to the default return (lines 270-278) which returns the HOSTED_NOTICE message, indicating the actual implementation is on a remote server via HOSTED_URL.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const name = request.params.name
      if (name === "agentcentral_setup") {
        return {
          content: [
            {
              type: "text",
              text:
                `Hosted MCP endpoint:\n  ${HOSTED_URL}\n\n` +
                `Setup guide:\n  ${SETUP_URL}\n\n` +
                `Add this to your client config:\n` +
                `{\n  "mcpServers": {\n    "agentcentral": {\n      "url": "${HOSTED_URL}",\n      "headers": { "Authorization": "Bearer ac_live_<YOUR_API_KEY>" }\n    }\n  }\n}`,
            },
          ],
          isError: false,
        }
      }
      return {
        content: [
          {
            type: "text",
            text: HOSTED_NOTICE,
          },
        ],
        isError: false,
      }
    })
  • HOSTED_NOTICE constant explaining that the 87 tools (including get_budget_pacing) are only available through the remote streamable-HTTP MCP endpoint, not implemented locally.
    const HOSTED_NOTICE =
      `agentcentral exposes 87 production tools across Amazon Ads, Seller Central, ` +
      `inventory, orders, catalog, ranking, finance, and fulfillment. They are only ` +
      `available through the remote streamable-HTTP MCP endpoint at ${HOSTED_URL}.\n\n` +
      `This stdio package is an introspection stub. To connect Claude, ChatGPT, ` +
      `Cursor, OpenClaw, or another MCP client to the live server, follow the setup ` +
      `guide at ${SETUP_URL}.`
  • HOSTED_URL constant pointing to the remote server that actually implements get_budget_pacing.
    const HOSTED_URL = "https://mcp.agentcentral.to/mcp"
Behavior4/5

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

With no annotations, the description carries the full burden. It clearly states the tool is a read operation and lists the outputs. Though it does not mention safety or side effects, the verb 'Read' and the nature of the data (budget pacing) strongly imply no destructive side effects, making it sufficiently transparent.

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?

The description is a single, well-structured sentence with no redundancy. Every part delivers value: verb, resource, and listed outputs.

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?

For a zero-parameter tool with no output schema, the description is complete. It tells exactly what the tool reads and what data it returns. No additional information is needed for an AI agent to invoke it correctly.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to add parameter meaning since none exist.

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 uses a specific verb 'Read' and resource 'campaign budget pacing', and lists the exact data returned (budget consumed by hour, time-out-of-budget percentage, pacing alerts). This clearly distinguishes it from sibling tools like get_campaign_performance which focus on different metrics.

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?

The description implies usage for reading budget pacing data, but there is no explicit guidance on when to use this tool versus alternatives (e.g., get_campaign_performance) or when not to use it. Users must infer its purpose from the title and context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentcentral-to/agent-central-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server