postcopilot_export_profileExport up to 20 recent posts from a Threads user profile. Returns structured post data including text, likes, replies, reposts, and timestamps. Provide a profile URL like https://www.threads.com/@username.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The Threads profile URL (e.g. https://www.threads.com/@username) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It explains the output (structured post data) and the limit (20 posts). It does not mention authentication, rate limits, or side effects, but for a simple read-only export, the provided detail is adequate.
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?
Two sentences: first states purpose and scope, second gives usage example. No extraneous words.
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 the tool has a single parameter and no output schema, the description covers the essential purpose, output format, and input example. It could mention authentication or edge cases, but is fairly complete for its simplicity.
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?
Schema coverage is 100% and already describes the 'url' parameter with an example. The tool description repeats the example, adding minimal new semantic value beyond the 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?
The description uses a specific verb 'export' and resource 'Threads user profile posts', and includes a limit ('up to 20 recent posts'). It clearly distinguishes from sibling tools like export_followers and export_following.
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?
The description provides a concrete example of the required input URL format, guiding correct invocation. It does not explicitly state conditions when not to use the tool or mention alternatives, but sibling context implicitly differentiates use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: downloading videos, exporting followers/following/profile, generating posts, and reading guides. No overlap or ambiguity.
All tools follow a consistent 'postcopilot_verb_noun' pattern with snake_case, making them predictable and easy to distinguish.
With 6 tools, the server is well-scoped for Threads social media tasks—covering content retrieval, analytics, and creation without being over- or under-sized.
Core workflows (exporting data, generating posts, reading guides) are covered. Minor gaps exist, such as no direct posting or interaction tools, but the surface is coherent for the stated purpose.