Pull an image or video from a public https URL into Postlia storage. Returns the storage URL and media type, ready for create_post. PNG, JPEG, WebP, GIF, MP4, WebM, MOV, max 25 MB.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public https URL of the file |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool pulls from a public URL, returns a storage URL and media type, supports a specific set of formats, and enforces a size limit. This goes beyond a simple 'upload media' statement and provides meaningful behavioral context, though it omits potential error conditions.
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?
The description is two sentences, front-loaded with the main action and purpose. It efficiently conveys the operation, return value, integration point, and key constraints without redundant filler.
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?
For a tool with a single parameter and no output schema, the description provides complete information: what it does, what constraints apply, what is returned, and how it fits into the workflow (create_post). No annotations or additional structure leaves gaps.
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?
The schema covers the only parameter (url) with a basic description. The description adds value by explaining what type of content is expected (image or video), listing supported formats, and indicating the size limit, which clarifies the URL's content requirements 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 clearly identifies the tool's purpose with a specific verb ('Pull') and resource ('image or video from a public https URL into Postlia storage'). It distinguishes itself from all sibling tools, which focus on posting and drafts, not media ingestion.
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 implies a clear use case ('ready for create_post') and specifies constraints (public HTTPS, supported formats, max 25 MB). It doesn't explicitly name alternative tools, but no sibling upload tool exists, so the context is sufficient.
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 targets a unique resource and action: drafts, scheduled posts, published posts, accounts, analytics, quota, and queue info are all clearly separated. No two tools overlap in purpose; even similar-sounding ones like list_scheduled_posts and list_published_posts are distinct.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_post, list_drafts, get_posting_quota). The use of 'list_' for collections and 'get_' for single items/summaries is predictable and logical.
14 tools is well within the ideal 3-15 range and appropriately covers the domain of social media post management, scheduling, drafts, analytics, and account inspection. Each tool serves a distinct function without redundancy.
The surface covers the full lifecycle of posts and drafts: create, read, update, delete, schedule, cancel, and reschedule. Minor gaps exist, such as no direct way to convert a draft into a post, but this can be worked around by copying content.