sprkly_get_post_statusFull detail for one post: status, targets, scheduled and published times, permalink, and the failure reason if it did not publish. Media comes back as mediaIds in slide order, not as links. Ids and profile ids are plumbing: talk to the user about accounts by handle and about posts by their caption, and do not read ids out unless they ask for one.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | The scheduled post id. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only behavior, so the description appropriately focuses on additional behavioral details: media is returned as mediaIds in slide order rather than links, failure reasons are included when relevant, and IDs are presented as plumbing to avoid exposing them to users. This adds value beyond the annotations without contradicting them.
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 three sentences long and front-loaded with the core purpose. Every sentence contributes essential information: what is returned, the media format quirk, and the user-facing communication guideline. No filler is present.
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 simple one-parameter read-only tool and no output schema, the description covers the important return values (status, targets, times, permalink, failure reason) and flags the mediaIds behavior and ID-handling convention. It is sufficiently complete for an agent to invoke the tool and interpret the result correctly.
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 documents the single post_id parameter with 100% coverage, so the baseline is 3. The description adds a note about not reading IDs aloud, which is useful interaction guidance, but it does not add significant semantic detail about the parameter itself.
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 names a specific verb and resource ('Full detail for one post') and enumerates what is returned, distinguishing it from sibling tools like list_scheduled_posts or get_post_approval_status. The phrase 'one post' and the detailed result fields make the tool's purpose unmistakable.
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 establishes a clear use case: retrieving full detail for a single post. It does not explicitly name alternative tools or exclusion criteria, but the 'one post' scoping contrasts with list-oriented siblings, giving clear context for when it applies.
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.