Skip to main content
Glama

x_api_article_create_draft

Create a draft article on X. This tool initiates the X API operation to create a new unpublished article. Use it to prepare content before publishing.

Instructions

Create draft Article. Use when: Create draft Article. 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 tweet.write; 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: no endpoint-specific parameters; 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_article_create_draft","arguments":{"scopeTenantId":"default","scopeUserId":"default","body":{}}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
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 discloses mutating/high-risk status, required OAuth scopes/token types, environment-selection behavior, common failure conditions, and a safety warning. This fully compensates for absent annotations.

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?

Labeled sections make the content scannable and front-loaded, but there is mild redundancy ('Create draft Article' repeated and risk stated twice). Still, every section earns its place given the lack of annotations.

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?

The description includes expected response shape, failure conditions, recommended tools, and an example, which is strong for a mutating API wrapper. The main shortfall is incomplete parameter coverage for authorizationKey/preferredAuthType and body payload details, preventing a perfect score.

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?

The description explains scopeTenantId/scopeUserId/scopeAccountId selection and credentialKey selection, which adds value beyond the bare schema. However, authorizationKey and preferredAuthType are not explained, and body is only described as 'documented request payload' without structure. With 0% schema coverage, this leaves significant gaps.

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 'Create draft Article.' states a specific verb and resource, clearly distinguishing this from the sibling x_api_article_publish. Even without a title, the purpose is unambiguous.

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?

Explicit 'Use when' and 'Do not use when' sections give clear invocation context and steer exploration to x_schema_discovery/x_query_suggestion. It could more directly contrast with x_api_article_publish, but the draft/publish naming separation plus alternatives is adequate.

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