Skip to main content
Glama

search_profile

Read-only

Read recent posts from an X profile by handle, profile URL, or tweet URL to monitor competitors and specific individuals.

Instructions

Read recent posts from ONE X profile. profile takes a handle ("@nasa" or "nasa"), a profile URL, or a tweet URL (which resolves to its author). Read-only (draft mode does not apply, nothing is posted), but it reuses the account's browser session. account defaults to the first active configured account. Use this to watch specific people and competitors, and to re-read one of your own published posts for its public counts; use search_tweets for topic and keyword discovery. Profile timelines include pinned posts and reposts, so check user_handle before treating a result as the profile owner's own writing. include_images=true additionally attaches the first photo of up to 5 posts as image content (bounded); the per-post media URLs + alt text are always present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
accountNo
profileYes
include_imagesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond annotations (readOnlyHint), it explains that draft mode does not apply, nothing is posted, and it reuses the account's browser session. Notes default account behavior.

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?

Well-structured: starts with main action, then details. A bit long but justified by complexity. Could tighten slightly.

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?

Given output schema exists, complete coverage of purpose, usage, and behavioral aspects. Provides enough for agent to use correctly.

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?

With 0% schema coverage, the description compensates significantly: explains profile input varieties, include_images effect, and default account. However, limit parameter is not explained.

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 it reads recent posts from one X profile, specifying input types (handle, profile URL, tweet URL). It distinguishes from sibling tool search_tweets for topic discovery.

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 says when to use (watch specific people/competitors, re-read own posts) and when not (use search_tweets). Also warns about pinned posts and reposts, advising to check user_handle.

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/ihuzaifashoukat/x-use'

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