Skip to main content
Glama
Prototypr

Feedbagel MCP Server

Official
by Prototypr

list_webhooks

Retrieve all webhook subscriptions registered to your account. Quickly view and manage your configured webhooks.

Instructions

[read] List all webhook subscriptions owned by the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_webhooks' tool. It makes a GET request to /api/v1/webhooks with no input params.
    {
      name: "list_webhooks",
      description: "List all webhook subscriptions owned by the user.",
      scope: "read",
      inputSchema: z.object({}),
      handler: (_, c) => c.request("GET", "/api/v1/webhooks"),
    },
  • Input schema for list_webhooks: an empty object (no parameters). The tool has scope 'read'.
    name: "list_webhooks",
    description: "List all webhook subscriptions owned by the user.",
    scope: "read",
    inputSchema: z.object({}),
  • src/tools.ts:27-213 (registration)
    The TOOLS array containing all tool definitions, including list_webhooks as one entry. Each entry defines name, description, scope, inputSchema, and handler.
    export const TOOLS: ToolDef[] = [
      {
        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"),
      },
      {
        name: "follow_feed",
        description:
          "Add a feed to the user's follow list. Idempotent. Counts against the subscription cap.",
        scope: "write",
        inputSchema: FeedIdInput,
        handler: (input, c) => c.request("POST", "/api/v1/follow", input),
      },
      {
        name: "unfollow_feed",
        description: "Remove a feed from the user's follow list.",
        scope: "write",
        inputSchema: FeedIdInput,
        handler: ({ feed_id }: any, c) =>
          c.request("DELETE", `/api/v1/follow/${feed_id}`),
      },
      {
        name: "list_webhooks",
        description: "List all webhook subscriptions owned by the user.",
        scope: "read",
        inputSchema: z.object({}),
        handler: (_, c) => c.request("GET", "/api/v1/webhooks"),
      },
      {
        name: "create_webhook",
        description:
          "Create a webhook subscription. The response includes webhook_secret ONCE; the bot must persist it for HMAC validation. Counts against the subscription cap.",
        scope: "write",
        inputSchema: z.object({
          webhook_url: z.string().url(),
          subscriber_name: z.string().max(120).optional(),
          notes: z.string().max(500).optional(),
        }),
        handler: (input, c) => c.request("POST", "/api/v1/webhooks", input),
      },
      {
        name: "delete_webhook",
        description: "Delete a webhook subscription and all its feed attachments.",
        scope: "write",
        inputSchema: WebhookIdInput,
        handler: ({ webhook_id }: any, c) =>
          c.request("DELETE", `/api/v1/webhooks/${webhook_id}`),
      },
      {
        name: "pause_webhook",
        description:
          "Pause deliveries for a webhook subscription. Existing attachments stay; the poller skips this subscriber until resumed.",
        scope: "write",
        inputSchema: WebhookIdInput,
        handler: ({ webhook_id }: any, c) =>
          c.request("POST", `/api/v1/webhooks/${webhook_id}/pause`),
      },
      {
        name: "resume_webhook",
        description: "Resume deliveries for a paused webhook subscription.",
        scope: "write",
        inputSchema: WebhookIdInput,
        handler: ({ webhook_id }: any, c) =>
          c.request("POST", `/api/v1/webhooks/${webhook_id}/resume`),
      },
      {
        name: "attach_feed_to_webhook",
        description:
          "Attach a feed to a webhook subscription so its new entries get delivered.",
        scope: "write",
        inputSchema: WebhookIdInput.merge(FeedIdInput),
        handler: ({ webhook_id, feed_id }: any, c) =>
          c.request("POST", `/api/v1/webhooks/${webhook_id}/feeds`, {
            feed_id,
          }),
      },
      {
        name: "detach_feed_from_webhook",
        description: "Stop delivering a feed's entries to a webhook subscription.",
        scope: "write",
        inputSchema: WebhookIdInput.merge(FeedIdInput),
        handler: ({ webhook_id, feed_id }: any, c) =>
          c.request(
            "DELETE",
            `/api/v1/webhooks/${webhook_id}/feeds/${feed_id}`,
          ),
      },
      {
        name: "me",
        description:
          "Return the authenticated account's email, plan, and status. Use as a smoke test before other calls.",
        scope: "read",
        inputSchema: z.object({}),
        handler: (_, c) => c.request("GET", "/api/v1/me"),
      },
    
      // --- discovery (public reads, but the MCP still authenticates) -------
    
      {
        name: "search_feeds",
        description:
          "Search the feed catalog by keyword. Matches feed titles, urls, and hostnames. Returns up to 20 results with recency stats.",
        scope: "read",
        inputSchema: z.object({
          query: z.string().min(1).max(120),
        }),
        handler: ({ query }: any, c) =>
          c.request(
            "GET",
            `/api/v1/search-feeds/keyword/${encodeURIComponent(query)}`,
          ),
      },
      {
        name: "search_feeds_by_url",
        description:
          "Find feeds at a specific hostname or URL fragment. Use this when the user already knows the site (e.g. 'theverge.com') and wants its feeds.",
        scope: "read",
        inputSchema: z.object({
          url_or_host: z.string().min(1).max(200),
        }),
        handler: ({ url_or_host }: any, c) =>
          c.request(
            "GET",
            `/api/v1/search-feeds/url/${encodeURIComponent(url_or_host)}`,
          ),
      },
      {
        name: "get_host_metadata",
        description:
          "Get metadata (title, description, favicon, feed list) for a host domain.",
        scope: "read",
        inputSchema: z.object({
          host: z.string().min(1).max(200),
        }),
        handler: ({ host }: any, c) =>
          c.request(
            "GET",
            `/api/v1/host/${encodeURIComponent(host)}/metadata`,
          ),
      },
      {
        name: "list_entries",
        description:
          "List recent entries across all feeds, paginated. Use sort_by='published' (default) for newest first.",
        scope: "read",
        inputSchema: z.object({
          page: z.number().int().positive().default(1),
          per_page: z.number().int().min(1).max(100).default(20),
          sort_by: z.enum(["published", "created"]).default("published"),
          sort_order: z.enum(["asc", "desc"]).default("desc"),
        }),
        handler: (input: any, c) => {
          const qs = new URLSearchParams({
            page: String(input.page),
            per_page: String(input.per_page),
            sort_by: input.sort_by,
            sort_order: input.sort_order,
          }).toString();
          return c.request("GET", `/api/v1/entries?${qs}`);
        },
      },
      {
        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}`),
      },
      {
        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)}`),
      },
    ];
Behavior3/5

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

Includes [read] hint indicating read-only behavior. However, with no annotations provided, the description could disclose more traits like data scope or performance considerations.

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, no wasted words. Front-loaded with purpose.

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?

Given no parameters and no output schema, description is adequate. Could mention pagination or sorting, but not critical for a simple list operation.

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 in input schema. Baseline set to 4 per instructions. Description adds no parameter info, but none needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states list all webhook subscriptions owned by user. Verb 'list' and resource 'webhook subscriptions' are explicit. Distinguishes from siblings by user scope, but does not explicitly differentiate from all related tools.

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 on when to use this tool versus alternatives. Does not mention any context or prerequisites for invoking this tool.

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