Skip to main content
Glama
pushpad

Pushpad MCP

Official
by pushpad

subscriptions_update

Update a push subscription's UID or tags to associate it with a specific user or audience segment for targeted notifications.

Instructions

To update a subscription, send a PATCH request to /projects/PROJECT_ID/subscriptions/SUBSCRIPTION_ID.

The subscription will be updated using the provided information.

The response body will contain a JSON object with the attributes of your subscription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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.
subscription_idYesThe ID of a subscription.
project_id__pathYesThe ID of a project. (Path parameter)

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 must disclose behavior. It correctly indicates this is a mutation operation ('update') and describes the response format ('JSON object with attributes'). However, it doesn't state whether updates are partial or full replacements, or what happens if required fields are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (3 sentences) but could be more concise. The first sentence redundantly explains the HTTP method in the description when the schema already implies it. The second sentence is unnecessary. The third sentence is acceptable but could be merged.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description covers the basic purpose and response shape. However, for a relatively simple update tool with no nested objects, it's missing key details: whether this is a partial update, required fields, idempotency, and error conditions. The schema's completeness partially compensates but behavioral gaps remain.

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 input schema has 100% coverage, with detailed descriptions for each parameter including examples and explanations for uid, tags, endpoint, etc. The description adds no additional parameter info, but given perfect schema coverage, the baseline is 3. The description earns a 4 because the schema itself is exceptionally rich and clear for all parameters.

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 clearly states the tool is for updating a subscription via a PATCH request, which is a specific verb-resource combination. However, it doesn't differentiate from the specific sibling tool 'subscriptions_delete' or 'subscriptions_create' but it's distinct from 'notifications_*' and 'projects_*' 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?

The description provides no guidance on when to use this tool versus alternatives like 'subscriptions_create' or 'subscriptions_delete'. It mentions neither prerequisites (e.g., subscription must exist) nor exclusions (e.g., fields that cannot be updated after creation).

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