Skip to main content
Glama

Identify an X URL

x_resolve_url
Read-only

Identify whether an X (Twitter) URL points to a profile or tweet, returning the handle or numeric ID for use with other X tools. Works offline without fetching the page.

Instructions

Identify what an X (formerly Twitter) URL points at before fetching it. Give any x.com or twitter.com URL (mobile links, query params, /i/web/status forms are fine); get back {type: profile|tweet, id, handle, canonical_url}. Tweet URLs yield the numeric id for x_get_tweet; profile URLs yield the handle for x_get_profile or x_get_tweets. Costs 2 credits and parses offline without fetching the page. t.co short links cannot be expanded offline and return INVALID_INPUT telling you so; expand them in your own browser step first. Skip this tool when you already have a handle or tweet id: the other X tools accept those directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAn X URL, e.g. https://x.com/nasa/status/2054497961162478079 or https://twitter.com/nasa.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
usageYes
commonYes
entityYes
platformYes
freshnessYes
data_as_ofYes
canonical_urlYes
schema_versionYes
platform_fieldsYes
Behavior5/5

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

Adds significant context beyond annotations: costs 2 credits, parses offline without fetching the page, and t.co links return INVALID_INPUT. No contradiction with readOnlyHint annotation.

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?

Description is concise (3 sentences) and well-structured, with the most critical information front-loaded. Every sentence adds unique value.

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?

Covers all necessary aspects: purpose, usage, limitations (t.co), cost, and referral to sibling tools. Output schema exists so description needn't detail return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description elaborates on acceptable URL formats (mobile, query params, /i/web/status), adding value beyond the schema's basic description.

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 description clearly states the tool resolves X URLs to determine if they point to a profile or tweet, returning type, id, handle, and canonical URL. It distinguishes from sibling tools like x_get_tweet and x_get_profile.

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?

Explicitly tells when to use (before fetching a URL) and when not to (skip if handle or tweet ID already known). Provides alternative tools (x_get_tweet, x_get_profile, x_get_tweets) and warns about t.co short links requiring expansion.

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/veezeehq/veezee-mcp'

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