sprkly_export_automation_templateDownload one Instagram auto reply as a shareable template. The file holds the trigger, the keyword and the message, and never a post id, a profile id or any account details, so it is safe to send to someone else. An auto reply that is still a draft has nothing published to export.
| Name | Required | Description | Default |
|---|---|---|---|
| automation_id | Yes | The automation id to export. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already mark the tool as read-only, and the description adds useful behavioral context beyond this: the exported file excludes sensitive IDs and account details, making it safe to share. It also notes that drafts cannot be exported. This goes beyond the annotation signal.
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 short and front-loaded, with the main action stated first. The final sentence about drafts is slightly awkward and less direct, but the overall structure is tight and economical.
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 simple single-parameter read-only tool without an output schema, the description does a good job: it defines the output as a shareable template containing trigger, keyword, and message, and notes a key limitation. A bit more detail on the exact download behavior could help, but nothing critical is missing.
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 input schema fully describes the only parameter, 'automation_id', with 'The automation id to export.' The description adds context about what an auto reply is and what the template contains, but it does not meaningfully expand on the parameter's meaning beyond the schema. Baseline 3 applies because schema coverage is 100%.
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 states a specific action ('Download one Instagram auto reply as a shareable template') and identifies the resource and content. It is distinct from the sibling import tool, but it does not explicitly differentiate itself from any sibling in the description.
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 purpose of sharing a safe, non-sensitive template implies when to use this tool, and the draft limitation hints at a boundary, but it does not explicitly describe when to use an alternative or provide a when-not-to-use guide.
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.
Most tools target distinct resources and actions, and detailed descriptions make subtle differences clear. Minor ambiguity exists between sprkly_list_profiles and sprkly_list_connected_social_accounts, and between sprkly_get_post_status and sprkly_get_post_approval_status, but the descriptions provide enough context to disambiguate.
All tools share the sprkly_ prefix and use a snake_case verb_noun pattern. Read operations are consistently split between get_ for singular/detail and list_ for plural collections, with action verbs like schedule, draft, delete, request, and validate following the same clear style.
18 tools is on the heavier side, but the server covers a broad social media workflow spanning scheduling, approvals, analytics, billing, and automation templates. A few tools are explicitly optional, like sprkly_add_media_from_url and sprkly_get_tiktok_posting_options, so the set could be tightened slightly, but the count remains defensible for the scope.
The core post lifecycle is well covered: draft, validate, schedule, update, delete, get status, and approval flow. Minor gaps exist around draft/media library management and automation template listing/deletion, but agents can accomplish the main scheduling tasks without dead ends.