Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_profile

Fetch a public Threads profile by username to get name, bio, avatar URL, follower count, and thread count. Returns 404 if the profile is unavailable.

Instructions

Retrieve a public Threads profile. Returns a public Threads profile by username (with or without a leading @): name, profile URL, biography, avatar URL, followers_count and threads_count. Counts are derived from the compact figures shown on the profile page. An unavailable profile returns 404.

Input Schema

NameRequiredDescriptionDefault
usernameYesThreads username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses returned fields, that counts are derived from compact page figures, and that unavailable profiles return 404, but it does not mention authentication needs, rate limits, or behavior for private profiles.

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?

Front-loaded and efficiently sized in three sentences. There is minor repetition between the first two sentences, but every sentence otherwise earns its place by listing return fields and error behavior.

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?

For a one-parameter lookup tool with no output schema and no annotations, the description is nearly complete: it names the input, lists key return fields, explains count derivation, and documents the 404 case. It could be fuller on auth or limitations, but nothing critical is missing for correct invocation.

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 description coverage is 100% and the parameter is minimally described as 'Threads username'. The description adds meaningful syntax guidance beyond the schema by stating the username may be provided with or without a leading '@'.

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: retrieve a public Threads profile by username. It clearly identifies what is returned, though it does not explicitly differentiate itself from sibling profile subresource tools such as threads_profile_posts or threads_profile_media.

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?

The purpose implies usage for looking up a Threads profile by username, but there is no explicit when-to-use guidance, no mention of alternatives, and no conditions for selecting this tool over sibling Threads profile tools. Adequate but with clear gaps.

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