Veezee: LinkedIn people & company data for agents

Get an X profile

x_get_profile

Read-only

Fetch one X account's profile: name, bio, location, website, follower/following counts, tweet and media counts, verification state, and join date. identifier accepts a screen name without the @ (e.g. 'nasa'), a full x.com or twitter.com profile URL, or the numeric account id; numeric strings are treated as ids, and the rare all-digit handle can be forced with by='screen_name'. Costs 4 credits. The returned platform_fields.id is stable across handle changes; store it for repeat lookups. To find accounts by topic use x_search type=people, and to read what an account posts use x_get_tweets; this tool returns no tweets.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`by`	No	Force how identifier is interpreted; auto-detected when omitted.
`freshness`	No	recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it.	recent
`identifier`	Yes	Screen name without the @ (e.g. 'nasa'), profile URL, or numeric account id.
`max_credits`	No	Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`usage`	Yes
`common`	Yes
`entity`	Yes
`platform`	Yes
`freshness`	Yes
`data_as_of`	Yes
`canonical_url`	Yes
`schema_version`	Yes
`platform_fields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes beyond readOnlyHint and openWorldHint annotations by detailing credit costs, caching behavior (recent vs realtime), trial key limitations, refund policy, and the stability of the returned id. No contradiction with 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?

Single paragraph is dense and front-loaded with purpose. Every sentence adds value, but could be slightly more structured (e.g., bullet points) for easier scanning given the amount of detail.

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 aspects: purpose, identifier handling, parameter details, costs, caching, authentication implications, sibling tool distinctions, and output stability. With output schema present, no need to detail return values further.

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 description coverage is 100%, but the description adds significant value: explains acceptable identifier formats (screen name, URL, numeric ID), how the 'by' parameter forces interpretation, freshness credit/caching details, and max_credits spend ceiling logic.

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 'Fetch one X account's profile' and lists specific fields returned. It distinguishes from siblings: x_search (type=people) for finding accounts by topic and x_get_tweets for reading posts.

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?

Provides explicit guidance on when to use (fetch profile) and when not to (use x_search or x_get_tweets). Also explains identifier formats and interpretation, including edge cases like all-digit handles.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Veezee: LinkedIn people & company data for agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?