Skip to main content
Glama

get_feed_uploads

Get upload history for a product feed to monitor past uploads and track feed status.

Instructions

Get upload history for a product feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feed_idYesProduct feed ID
fieldsNoComma-separated fields to return
limitNoNumber of results to return
afterNoPagination cursor for next page

Implementation Reference

  • Registers the 'get_feed_uploads' tool on the MCP server. The handler accepts feed_id, optional fields, limit, and after parameters, makes a GET request to /{feed_id}/uploads, and returns the upload history data with rate limit info.
    server.tool(
      "get_feed_uploads",
      "Get upload history for a product feed.",
      {
        feed_id: z.string().describe("Product feed ID"),
        fields: z.string().optional().describe("Comma-separated fields to return"),
        limit: z.number().optional().default(25).describe("Number of results to return"),
        after: z.string().optional().describe("Pagination cursor for next page"),
      },
      async ({ feed_id, ...params }) => {
        try {
          const { data, rateLimit } = await client.get(`/${feed_id}/uploads`, { ...params });
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Zod schema for the tool's input parameters: feed_id (required string), fields (optional string), limit (optional number, default 25), after (optional string for pagination).
    {
      feed_id: z.string().describe("Product feed ID"),
      fields: z.string().optional().describe("Comma-separated fields to return"),
      limit: z.number().optional().default(25).describe("Number of results to return"),
      after: z.string().optional().describe("Pagination cursor for next page"),
    },
  • Tool is registered via server.tool() as part of the registerFeedTools function, which takes an McpServer and AdsClient as dependencies.
    server.tool(
      "get_feed_uploads",
      "Get upload history for a product feed.",
      {
        feed_id: z.string().describe("Product feed ID"),
        fields: z.string().optional().describe("Comma-separated fields to return"),
        limit: z.number().optional().default(25).describe("Number of results to return"),
        after: z.string().optional().describe("Pagination cursor for next page"),
      },
      async ({ feed_id, ...params }) => {
        try {
          const { data, rateLimit } = await client.get(`/${feed_id}/uploads`, { ...params });
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Imports: zod for schema validation, McpServer from the MCP SDK, and AdsClient from the services layer.
    import { z } from "zod";
    import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { AdsClient } from "../services/ads-client.js";
Behavior2/5

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

Without annotations, the description must disclose behavioral traits, but it only states 'Get upload history'. It does not mention that the operation is read-only, does not explain pagination (despite 'limit' and 'after' parameters), nor does it describe ordering or default behavior.

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?

The description is a single, efficient sentence. However, it could include more informative context without being overly long, so it is not a perfect 5.

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?

With no output schema, the description should explain return values or structure, but it does not. It covers the basic purpose but omits details about the response format, which is a gap for a tool with 4 parameters.

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?

Since the input schema covers all 4 parameters (100% description coverage), the baseline is 3. The description adds no extra meaning beyond the schema, e.g., it doesn't clarify that 'fields' controls which properties are returned.

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 clearly states the verb 'Get' and the resource 'upload history for a product feed', making the tool's purpose unambiguous. It distinguishes from sibling tools like 'upload_feed' and 'create_feed'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'list_feeds' or 'upload_feed'. There is no mention of prerequisites or conditions for use.

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/mikusnuz/meta-ads-mcp'

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