Skip to main content
Glama

List Webhook Subscriptions

astroway_webhooks_webhooks

List all active webhook subscriptions for the authenticated user.

[Group: Webhooks] [Endpoint: GET /v1/webhooks] [Cost: 10 credits (Tier 1)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_webhooks_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
subscriptionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / subscriptions / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "active": {
      -              "anyOf": [
      -                {
      -                  "type": "boolean"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "created_at": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "event": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "failure_count": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "id": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "last_delivery_at": {
      -              "anyOf": [
      -                {},
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "last_status_code": {
      -              "anyOf": [
      -                {},
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "url": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "active": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "created_at": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "event": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "failure_count": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "id": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "last_delivery_at": {
      +              "anyOf": [
      +                {},
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "last_status_code": {
      +              "anyOf": [
      +                {},
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "url": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The metadata block adds genuinely useful behavior beyond the annotations: endpoint, tier, and a 10-credit cost, which explains why readOnlyHint is false for an otherwise read-shaped call. However, the description calls this a plain 'List' operation without acknowledging the non-idempotent/credit-consuming side effect, leaving a mild tension with the annotations unaddressed; pagination and result limits are also unstated.

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?

One sentence states the purpose, and the bracketed group/endpoint/cost lines are compact, scannable, and front-loaded with the most decision-relevant facts. No filler, though the tag block is slightly mechanical.

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 zero-required-parameter list tool, the description covers scope, endpoint, and cost, and an output schema exists so return values need no explanation. The remaining gaps — pagination behavior and whether a failed call still bills credits — are minor for this complexity level.

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?

Schema description coverage is 100%, so 'fields' and 'precision' are already fully documented with examples and bounds. The description adds no parameter guidance of its own, which is acceptable given the schema does the work, but it means no extra meaning is contributed.

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?

The description states a specific verb and resource ('List all active webhook subscriptions') plus a scope qualifier ('for the authenticated user'), which cleanly separates it from astroway_webhooks_subscribe (creates) and astroway_webhooks_id (fetches one). It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 intent is clear enough that an agent can infer this is the discovery step before subscribing or fetching a specific webhook, but the description never says when to prefer it over astroway_webhooks_id or how it relates to astroway_webhooks_subscribe. No prerequisites, no exclusions, no alternatives named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources