get_profile
Retrieves Threads profile details including username, display name, and biography.
Instructions
Lay thong tin ho so Threads (username, ten, tieu su).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieves Threads profile details including username, display name, and biography.
Lay thong tin ho so Threads (username, ten, tieu su).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description specifies returned fields (username, name, bio) and implies no side effects for this read-only operation. However, it does not disclose authentication requirements or confirm it retrieves the user's own profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, clear sentence, no unnecessary words. Front-loaded with the action and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description adequately explains the tool's function and output fields. Could clarify that it returns the authenticated user's profile, but overall sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so the baseline is 4. The description adds value by explaining what the tool returns, which is beyond the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Get' and the resource 'profile information' with specific fields (username, name, bio), distinguishing it from sibling tools that handle posting or listing operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool or alternatives. The lack of parameters implies it retrieves the current user's profile, but this is not stated, leaving room for ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Maz1n0-zzz/threads-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server