Skip to main content
Glama

x_api_update_activity_subscription

Update an X activity subscription by providing its ID and a new payload. This mutates the subscription state, so supply valid scoped credentials and authorization before use.

Instructions

Update X activity subscription. Use when: Update X activity subscription. Do not use when: a more specific auth/configuration tool is required before the API call or you are only exploring; prefer x_schema_discovery or x_query_suggestion first. Risk: mutating, high-risk. Required permissions and prerequisites: bearer token Environment-selection behavior: scopeTenantId plus exactly one of scopeUserId or scopeAccountId choose the Vault/Postgres tenant principal used for auth resolution. credentialKey selects a non-default stored credential profile when present. Parameter formats and constraints: subscription_id (path, unknown, required); body is used for the documented request payload. Expected response shape: { ok, status, data: { method, path, url, status, contentType, authType, data } } Common failure conditions: missing scoped credentials in Vault, missing required API parameters, X API auth failures, rate limits, or unsupported multipart/body shape. Recommended prerequisite and follow-up tools: x_connection_info, x_schema_discovery, x_auth_upsert_principal_credentials, x_api_request. Safety warnings: This mutates X state. Validate scope, payload, and authorizationKey before use. Example: {"name":"x_api_update_activity_subscription","arguments":{"scopeTenantId":"default","scopeUserId":"default","subscription_id":"","body":{}}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
scopeUserIdNo
credentialKeyNo
scopeTenantIdNo
scopeAccountIdNo
subscription_idYes
authorizationKeyNo
preferredAuthTypeNo
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It discloses mutating/high-risk nature, bearer token requirement, scoped auth resolution behavior, expected response shape, and common failure conditions, going far beyond a minimal mention.

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?

Although long, the description is well-structured with labeled sections (Risk, Permissions, Environment-selection, Expected response, Failure conditions, Example), each providing unique and actionable information. The purpose is front-loaded, and no sentence is wasted.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, no annotations, no output schema), the description supplies essential context: response shape, failure modes, prerequisites, environment-selection behavior, and an example. This is a complete and highly usable description for an agent.

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?

Schema description coverage is 0%, so the description compensates by explaining subscription_id as a required path parameter, body as the request payload, and the scopeTenantId/scopeUserId/scopeAccountId selection logic. However, authorizationKey and preferredAuthType are not explained, leaving a minor gap in parameter semantics.

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 opening line 'Update X activity subscription' uses a specific verb and resource, clearly distinguishing this tool from sibling create/delete/get activity subscription tools. The purpose is immediately unambiguous, and the absence of a title does not detract from clarity.

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

Usage Guidelines5/5

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

The description explicitly states 'Use when' conditions and 'Do not use when' exclusions, even naming alternative tools like x_schema_discovery and x_query_suggestion. This provides clear decision guidance beyond the schema and annotations.

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/LesterAJohn/X-mcp'

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