Skip to main content
Glama
Prototypr

Feedbagel MCP Server

Official
by Prototypr

list_subscriptions

Retrieve a combined list of your feed follows and webhook subscriptions, each tagged as 'follow' or 'webhook'.

Instructions

[read] Unified list of the user's feed follows and webhook subscriptions. Each item is tagged kind: 'follow' or 'webhook'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'list_subscriptions' tool. Calls GET /api/v1/subscriptions via the FeedbagelClient. No input arguments required (empty schema).
    {
      name: "list_subscriptions",
      description:
        "Unified list of the user's feed follows and webhook subscriptions. Each item is tagged kind: 'follow' or 'webhook'.",
      scope: "read",
      inputSchema: z.object({}),
      handler: (_, c) => c.request("GET", "/api/v1/subscriptions"),
  • The tool definition including empty inputSchema (z.object({})), description, and read scope.
    {
      name: "list_subscriptions",
      description:
        "Unified list of the user's feed follows and webhook subscriptions. Each item is tagged kind: 'follow' or 'webhook'.",
      scope: "read",
      inputSchema: z.object({}),
  • src/index.ts:37-43 (registration)
    MCP server registration of all tools via ListToolsRequestSchema handler, which maps TOOLS to MCP tool format.
    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-70 (registration)
    CallToolRequestSchema handler that dispatches to the correct tool handler by name (including 'list_subscriptions').
    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) {
  • FeedbagelClient.request() - the helper used by the handler to make HTTP requests to the feedbagel API.
    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;
    }
Behavior3/5

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

No annotations provided; description includes a '[read]' tag indicating it's read-only, and mentions each item is tagged with 'kind'. Does not disclose pagination, auth requirements, or rate limits. Adequate but not detailed.

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?

Single sentence that conveys purpose and result format. No wasted words, front-loaded with key information.

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 no parameters and no output schema, description explains the unified list and kind tagging. Could mention pagination, but overall 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?

No parameters exist, input schema empty. Baseline per rules is 4. Description adds no param info but none needed.

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?

Clearly states it lists the user's feed follows and webhook subscriptions, distinguishing it from siblings like list_webhooks which shows only webhooks. Verb 'list' and resource 'subscriptions' are specific.

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?

Does not explicitly instruct when to use this vs alternatives like list_webhooks or follow_feed. The context implies it's for a unified view, but no direct when-to-use guidance.

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