Skip to main content
Glama
Threads MCP

Threads MCP

by kerwilgil

Get Threads profile

threads_get_profile
Read-onlyIdempotent

Fetches the authenticated Threads profile so you can identify the connected account and review its profile details.

Instructions

Read the authenticated Threads profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "threads_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
nameNo
usernameYes
biographyNo
profile_picture_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds only the authentication scoping constraint; it does not mention token requirements, rate limits, or that the result is the caller's own profile data.

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?

One short sentence, front-loaded with the verb and logically ordered. Nothing is wasted, though the brevity borders on under-specification rather than genuine crispness.

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?

With annotations covering the safety profile and an output schema documenting the return shape, the description only needs to establish what entity is fetched, which it does via 'authenticated Threads profile'. A note about auth prerequisites would make it complete, but nothing essential is missing.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the implicit scoping it already provides. Baseline 4 applies for a no-parameter tool.

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 and resource ('Read the authenticated Threads profile') and scopes it to the authenticated account. It doesn't explicitly contrast with siblings like threads_get_post, though the scope word 'authenticated' does most of the disambiguation work for a zero-parameter tool.

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 rather than stated: 'authenticated profile' signals this returns the caller's own account, not an arbitrary one. There is no explicit when-to-use or when-not guidance, and no mentions of alternatives such as threads_get_post.

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