Skip to main content
Glama
Prototypr

Feedbagel MCP Server

Official
by Prototypr

get_entry_by_slug

Retrieve a blog entry by its URL slug to access its content and metadata.

Instructions

[read] Fetch a single entry by its URL slug (matches /post/ on the site).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes

Implementation Reference

  • The handler function for get_entry_by_slug that makes a GET request to /api/v1/entry/slug/{slug} using the FeedbagelClient.
    handler: ({ slug }: any, c) =>
      c.request("GET", `/api/v1/entry/slug/${encodeURIComponent(slug)}`),
  • Input schema for get_entry_by_slug validating the 'slug' field as a string of 1-300 characters.
    inputSchema: z.object({
      slug: z.string().min(1).max(300),
    }),
  • src/tools.ts:203-212 (registration)
    Tool registration entry in the TOOLS array, defining name, description, scope, inputSchema, and handler for get_entry_by_slug.
      name: "get_entry_by_slug",
      description:
        "Fetch a single entry by its URL slug (matches /post/<slug> on the site).",
      scope: "read",
      inputSchema: z.object({
        slug: z.string().min(1).max(300),
      }),
      handler: ({ slug }: any, c) =>
        c.request("GET", `/api/v1/entry/slug/${encodeURIComponent(slug)}`),
    },
  • src/index.ts:37-43 (registration)
    MCP server registration: ListToolsRequestSchema handler that exposes tool definitions (including get_entry_by_slug) to the client.
    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)
    MCP server registration: CallToolRequestSchema handler that dispatches incoming tool calls (including get_entry_by_slug) to the matching 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,
              ),
            },
          ],
        };
      }
    });
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. The description only says 'Fetch a single entry' and includes a non-standard [read] tag implying no side effects. It fails to mention what happens if the slug is not found (returns null or error), any authentication requirements, rate limits, or other behavioral traits. This leaves significant gaps for an AI agent.

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, clearly front-loaded sentence with no unnecessary words. The [read] prefix immediately signals the tool's read-only nature. Every piece of information earns its place.

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 a simple tool with one parameter and no output schema, the description provides essential context (mapping to site URL pattern) and indicates read-only behavior. However, it does not mention expected return behavior on missing slug or any pagination limitations, which would make it more complete. Given the low complexity, it's nearly sufficient.

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 description adds meaning beyond the schema by explaining that 'slug' refers to a URL slug matching the pattern /post/<slug>. This clarifies the parameter's purpose and format, which the schema (type string, minLength, maxLength) does not convey. The schema coverage is 0%, so the description compensates well.

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 action ('Fetch') and the resource ('a single entry by its URL slug'). It includes a helpful context note ('matches /post/<slug> on the site') that distinguishes it from siblings like get_entry (probably by ID) and list_entries. The [read] prefix further clarifies it is safe.

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 does not explicitly state when to use this tool versus alternatives. It implies use when a slug is available, but no 'when not' or comparison to get_entry or search functions is provided. The reference to the site's URL pattern gives some context but is insufficient for an agent to decide this over similar tools.

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