Skip to main content
Glama
Prototypr

Feedbagel MCP Server

Official
by Prototypr

get_entry

Fetch a single RSS feed entry by its numeric ID. Get the complete details of that entry.

Instructions

[read] Fetch a single entry by numeric id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entry_idYes

Implementation Reference

  • The get_entry tool handler: takes an entry_id, makes a GET request to /api/v1/entry/{entry_id}.
    {
      name: "get_entry",
      description: "Fetch a single entry by numeric id.",
      scope: "read",
      inputSchema: z.object({
        entry_id: z.number().int().positive(),
      }),
      handler: ({ entry_id }: any, c) =>
        c.request("GET", `/api/v1/entry/${entry_id}`),
    },
  • Input schema for get_entry: requires a positive integer 'entry_id'.
    inputSchema: z.object({
      entry_id: z.number().int().positive(),
    }),
  • src/index.ts:37-43 (registration)
    Tools are registered with the MCP server via ListToolsRequestSchema handler, mapping TOOLS array to name/description/inputSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS.map((t) => ({
        name: t.name,
        description: `[${t.scope}] ${t.description}`,
        inputSchema: zodToJsonSchema(t.inputSchema, { target: "openApi3" }),
      })),
    }));
  • src/index.ts:45-86 (registration)
    CallToolRequestSchema handler: finds the tool by name from TOOLS array (including get_entry), validates input, and invokes handler.
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const tool = TOOLS.find((t) => t.name === req.params.name);
      if (!tool) {
        return {
          isError: true,
          content: [{ type: "text", text: `Unknown tool: ${req.params.name}` }],
        };
      }
      const parsed = tool.inputSchema.safeParse(req.params.arguments ?? {});
      if (!parsed.success) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: `Invalid arguments: ${parsed.error.message}`,
            },
          ],
        };
      }
      try {
        const result = await tool.handler(parsed.data, client);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (err) {
        const e = err as Error & { status?: number; body?: unknown };
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: JSON.stringify(
                { error: e.message, status: e.status, body: e.body },
                null,
                2,
              ),
            },
          ],
        };
      }
    });
  • FeedbagelClient class with the request() method that the get_entry handler calls (GET /api/v1/entry/{entry_id}).
    export class FeedbagelClient {
      private apiKey: string;
      private baseUrl: string;
    
      constructor(opts: ClientOptions) {
        if (!opts.apiKey) throw new Error("FEEDBAGEL_API_KEY is required");
        this.apiKey = opts.apiKey;
        this.baseUrl = (opts.baseUrl ?? DEFAULT_BASE).replace(/\/$/, "");
      }
    
      async request(
        method: string,
        path: string,
        body?: unknown,
      ): Promise<unknown> {
        const res = await fetch(`${this.baseUrl}${path}`, {
          method,
          headers: {
            Authorization: `Bearer ${this.apiKey}`,
            ...(body !== undefined ? { "content-type": "application/json" } : {}),
          },
          body: body !== undefined ? JSON.stringify(body) : undefined,
        });
    
        const text = await res.text();
        let json: unknown = undefined;
        try {
          json = text ? JSON.parse(text) : undefined;
        } catch {
          json = { raw: text };
        }
    
        if (!res.ok) {
          // Surface 429 and 4xx details verbatim so the agent sees the cap info.
          const err: Error & { status?: number; body?: unknown } = new Error(
            `HTTP ${res.status} ${res.statusText}`,
          );
          err.status = res.status;
          err.body = json;
          throw err;
        }
        return json;
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only indicates '[read]' to suggest a read operation, but fails to disclose other traits such as behavior on missing id, authentication requirements, or rate limits. The description is minimal and lacks transparency.

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, front-loaded sentence with no wasted words. It is appropriately short for a simple fetch operation, though it could slightly expand on key details without losing conciseness.

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?

The tool is straightforward (fetch by id) and has no output schema, but the description omits information about the return format or object structure. For a minimal viable description, it covers the essential purpose but lacks completeness on output expectations.

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 input schema has one parameter 'entry_id' with constraints (integer, exclusiveMinimum, minimum > 0), but schema description coverage is 0%. The description adds no extra meaning beyond 'numeric id'; it does not explain what the id represents or provide any additional context.

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?

Description explicitly states 'Fetch a single entry by numeric id', clearly indicating the operation (fetch) and resource (entry) with a specific identifier (numeric id). This distinguishes it from sibling tools like 'list_entries' (multiple) and 'get_entry_by_slug' (different identifier).

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 when a numeric id is available for a single entry, but provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or suggest other tools like 'get_entry_by_slug' for different id types.

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/Prototypr/feedbagel-mcp'

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