sprkly_list_scheduled_postsThe post queue, newest first, with a caption preview, targets, status and failure reason. Supports a status filter and cursor pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum posts to return. | |
| cursor | No | Pagination cursor. Pass the nextCursor value from a previous response. | |
| status | No | Filter by status. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already signals no side effects. The description adds behavioral details: ordering (newest first), response fields (targets, status, failure reason), and pagination via cursor. It does not mention permissions or rate limits, but for a read-only list operation, the provided info is sufficient.
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 one sentence but packs relevant details: ordering, output fields, filtering, and pagination. It is front-loaded with the core purpose ('post queue') and avoids redundancy with the schema. No fluff.
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 read-only list tool with 3 well-documented parametersable response shape, the description captures the essence: newest first, included fields, and pagination. Since there is no output schema, the description adequately hints at what the user will receive. No significant 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?
Schema coverage is 100% with descriptions for limit, cursor, and status. The description only reiterates 'status filter and cursor pagination' without adding new meaning. It does not clarify the limit parameter's default or max, but those are in the schema. Thus it meets the baseline but adds little.
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 ('list'), names the resource ('scheduled posts'), and provides concrete details: 'post queue, newest first, with a caption preview, targets, status and failure reason.' This clearly distinguishes it from sibling tools like get_post_status or get_post_approval, which are single-post lookups.
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 usage for viewing the post queue, and the mention of 'status filter' and 'cursor pagination' gives context for when to use this tool. However, it does not explicitly state when to avoid it (e.g., when you need a single post's details), but the 'post queue' phrasing makes the list purpose obvious enough.
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.