Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

threads_profile_topics

Read-only

List every public topic tag shown on one Threads profile, including tag id, canonical name, and community metadata. username accepts a profile handle. Use each name and id with threads_topic_search to retrieve matching public posts and authors, threads_search for text search, or threads_profile_reposts to browse reposts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "threads_profile_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesThreads username.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful scope context beyond that: the listing is exhaustive ('every') and restricted to 'public' tags, and it previews the response shape (id, canonical name, community metadata). No pagination or rate-limit detail, which keeps it short of a 5.

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?

Two tight sentences, zero filler. The purpose and returned fields are front-loaded, and downstream routing is consolidated into one sentence.

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?

An output schema exists, so return-format documentation is not required, and the annotations plus cross-tool routing cover the main agent needs. The only small gap is that it doesn't state prerequisites (e.g., whether the profile must be public or a handle format), which slightly limits completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema description coverage, the schema already documents 'username'. The description adds only that it 'accepts a profile handle', a marginal clarification over the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb ('List') and resource ('every public topic tag shown on one Threads profile') and enumerates the returned fields (tag id, canonical name, community metadata). An agent can distinguish it from threads_profile_posts, threads_profile_media, and threads_topic_search without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes downstream usage by naming three sibling tools (threads_topic_search for matching posts/authors, threads_search for text search, threads_profile_reposts for reposts) and the condition for each. It lacks an explicit 'when to choose this over threads_profile_posts' exclusion, so not quite a 5, but the guidance is concrete.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources