Skip to main content
Glama

x_api_delete_account_activity_subscription

Delete an account activity subscription for a user to stop webhook notifications about their activity.

Instructions

Delete subscription. Use when: Delete 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: webhook_id (path, unknown, required); user_id (path, unknown, required). 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_delete_account_activity_subscription","arguments":{"scopeTenantId":"default","scopeUserId":"default","webhook_id":""}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
webhook_idYes
scopeUserIdNo
credentialKeyNo
scopeTenantIdNo
scopeAccountIdNo
authorizationKeyNo
preferredAuthTypeNo
Behavior5/5

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

No annotations exist, and the description fully compensates by disclosing mutating high-risk behavior, required bearer token, environment-selection behavior for scopeTenantId/scopeUserId/scopeAccountId/credentialKey, common failure conditions, safety warnings, and expected response shape. This is a thorough behavioral disclosure exceeding typical descriptions.

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?

The description is well-structured with labeled sections (Risk, Required permissions, Environment-selection behavior, etc.), making key information easy to scan. Minor redundancy: 'Use when: Delete subscription' repeats the opening line. Overall each section earns its place, and the format is efficient for an agent.

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?

The description covers auth, failure, safety, response shape, and includes an example. However, the example omits the required user_id parameter, which is a critical gap for correct invocation. It also doesn't explicitly mention that this deletes an 'account activity' subscription. With 8 parameters and no output schema, the example flaw significantly undermines completeness.

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?

Input schema has 0% description coverage, so the description must explain all 8 parameters. It adds meaningful semantics for environment-selection parameters (scopeTenantId, scopeUserId, scopeAccountId, credentialKey) and identifies required path params. However, authorizationKey and preferredAuthType are left unexplained, and parameter formats are marked 'unknown', providing only partial compensation.

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

Purpose3/5

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

The description states 'Delete subscription.' which is a clear verb+resource, but uses the generic term 'subscription' rather than 'account activity subscription' from the tool name. It fails to differentiate from sibling tools like x_api_delete_activity_subscription or x_api_delete_activity_subscriptions_by_ids, making the purpose somewhat vague.

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?

Provides 'Use when' and 'Do not use when' sections with explicit advice to prefer x_schema_discovery or x_query_suggestion for exploration and to use auth/configuration tools first when needed. However, it does not compare against alternative subscription deletion tools, so an agent cannot decide when this tool is the best choice among similar siblings.

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