Skip to main content
Glama
pushpad

Pushpad MCP

Official
by pushpad

subscriptions_get

Retrieve details of a specific subscription by providing the project ID and subscription ID. Use this to view subscription information for a web push notification project.

Instructions

To show information about an individual subscription, send a GET request to /projects/PROJECT_ID/subscriptions/SUBSCRIPTION_ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe ID of a project.
subscription_idYesThe ID of a subscription.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoA unique identifier for each subscription. This is automatically generated upon subscription creation.
uidNoA user identifier associated with the subscription. You can use it to find the push subscription of a user and then send notifications to that specific user. You can choose any ID that makes sense for your application, like the ID of the user in your database.
authNoThe auth property of the push subscription object, as described in the W3C Push API. It is an authentication secret that an application server uses in authentication of its messages.
tagsNoTags associated with the subscription. You can use them to filter the push subscriptions and send notifications to a segment of your audience. You can add all tags that make sense for your application.
p256dhNoThe p256dh property of the push subscription object, as described in the W3C Push API. It is an elliptic curve Diffie-Hellman (ECDH) public key associated with the push subscription.
endpointNoThe push endpoint of a browser, as described in the W3C Push API. It is a URL where the application can deliver the push notifications that should be sent to the browser. An endpoint uniquely identifies the subscription.
created_atNoA time value given in ISO 8601 format. It represents when the subscription was created.
project_idNoThe ID of the project the subscription belongs to.
last_click_atNoA time value given in ISO 8601 format. It represents the last time that a notification sent to this subscription was clicked by the user. If there aren't any clicks on notifications yet, null is returned.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool performs a GET request, implying a read-only, idempotent operation. However, it does not cover other behavioral aspects like authentication requirements, error handling, or response format (though an output schema exists). This is basic but not rich.

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, well-structured sentence that front-loads the purpose ('show information') and includes the HTTP method and URL pattern. No unnecessary words; every part serves a clear function.

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 read tool with only two parameters and an existing output schema, the description is largely complete. It explains the resource and the retrieval method. It could mention that the subscription must exist or that it returns details, but the output schema covers the return structure. Minor gaps in usage context (e.g., no error scenarios) are acceptable given the tool's simplicity.

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 coverage is 100% with both parameters described ('The ID of a project' / 'The ID of a subscription'). The description adds the URL path template showing how parameters are used, but this is more structural than semantic. It does not provide examples, constraints, or relationships beyond the schema.

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 tool's purpose: 'show information about an individual subscription'. It also provides the HTTP method and URL format, making it specific. This distinguishes it from sibling tools like subscriptions_list (for listing multiple) and subscriptions_delete (for removal).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving a single subscription via a GET request. It does not explicitly state when not to use it or name alternatives, but the context of sibling tools (e.g., subscriptions_list) and the focus on 'individual' provides adequate guidance for most agents.

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/pushpad/pushpad-mcp'

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