postcopilot_generate_postGenerate a viral Threads post using a fine-tuned AI model. Provide a topic or idea and get a ready-to-post caption. Returns the generated text.
| Name | Required | Description | Default |
|---|---|---|---|
| model | No | AI model to use: 'gpt' (fine-tuned GPT, default) or 'llama' (Together AI Llama) | gpt |
| message | Yes | The topic, idea, or prompt for the Threads post |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose behavioral traits such as idempotency, rate limits, or safety, beyond stating it returns generated text.
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, front-loaded with purpose, no redundancy. Could be slightly more concise but overall efficient.
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?
Covers purpose and basic input, but lacks details on model selection, response format, or 'viral' optimization; no output schema to compensate.
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 description coverage is 100%; description adds minimal extra meaning beyond what the schema already provides (e.g., 'topic or idea' for message).
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 uses specific verb 'Generate' and resource 'Threads post', and distinguishes from sibling tools (download, export, read) clearly.
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?
Describes basic usage ('provide a topic or idea') but lacks explicit guidance on when to use this tool over alternatives or when not to use it.
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.