Skip to main content
Glama

x_api_create_account_activity_subscription

Create a subscription to monitor account activity in real time via a webhook, enabling your app to receive updates for tweets, DMs, and user events.

Instructions

Create subscription. Use when: Create 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: OAuth 2 user token with scopes dm.read, dm.write, tweet.read, users.read; OAuth 1a user 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); 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_create_account_activity_subscription","arguments":{"scopeTenantId":"default","scopeUserId":"default","webhook_id":"","body":{}}}

Input Schema

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

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

With no annotations, the description carries the full transparency burden. It explicitly states risk ('mutating, high-risk'), required permissions, common failure conditions, safety warnings, and environment-selection behavior. This thoroughly discloses the tool's behavioral traits.

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 (Use when, Do not use when, Risk, Required permissions, etc.), making it scannable. It is somewhat verbose, and 'Use when: Create subscription' is redundant, but each section essentially contributes useful information.

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 complexity (8 parameters, no output schema, no annotations), the description is highly complete. It covers expected response shape, common failure conditions, prerequisites, safety warnings, and provides an example. This is a well-rounded tool description.

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 webhook_id, body, and the scope parameters (scopeTenantId, scopeUserId, scopeAccountId, credentialKey). However, authorizationKey and preferredAuthType are not explicitly explained, though authorizationKey is mentioned in the safety warning. Significant meaning is added but not 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 says 'Create subscription,' which is a clear verb+resource statement. The tool name adds specificity about 'account activity,' but the description itself does not distinguish it from the sibling x_api_create_activity_subscription. It is clear but not fully differentiated.

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 includes a 'Do not use when' section with alternatives (x_schema_discovery, x_query_suggestion) and prerequisites, such as required OAuth scopes. However, the 'Use when' section is tautological ('Create subscription') and does not specify scenarios or differentiate from closely related sibling tools.

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