Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

x_profile

Retrieve public profile details for an X account by username, including bio, images, verification flags, and follower metrics. Returns 404 if profile is not public.

Instructions

Retrieve an X profile. Returns the public profile of an X account by username, with or without a leading @: name, description, location, avatar and banner images, creation date, verification flags, and metrics for followers, following, posts, likes, listed and media. verified_type and affiliate_label appear only when the account has them. Returns 404 when the profile is not public.

Input Schema

NameRequiredDescriptionDefault
usernameYesX username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the load and does well: it discloses the returned field set, notes that verified_type and affiliate_label are conditional, and states that a 404 is returned for non-public profiles. It stops short of mentioning auth or rate-limit behavior, but for a read tool this is solid.

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?

Three tight sentences, front-loaded with the action and then the return payload. The conditional-fields and 404 details each earn their place with no padding.

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?

No output schema and no annotations, and the description compensates well by enumerating return fields and the 404 case. It is nearly complete for a single-parameter lookup, with only minor edge behavior (e.g. metric absence) left implicit.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema by clarifying the username may be passed with or without a leading '@'. That directly removes a likely agent error.

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?

States a specific verb ('Retrieve') and resource ('an X profile') and enumerates the returned fields. It is clear what the tool does, but it never distinguishes itself from the sibling x_profile_posts, which an agent might reasonably confuse with it.

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?

Usage is implied by the request nature (look up an account by username), but there is no explicit statement of when to use this versus x_profile_posts or other X tools. No exclusions or prerequisites are given.

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

Deploy Server

Other Tools