Skip to main content
Glama
Sign In

sprkly-mcp

by app.sprkly
OverviewDiscussionsAdmin

Restore a post from the Bin

sprkly_restore_from_bin
Idempotent

Bring a deleted post back from the Bin. Only posts in the Bin, for 30 days after they were deleted (the Bin in the app shows the last 5). A scheduled post whose time has passed, or is under 2 minutes away, comes back as a draft, so it never goes out on its own: ask the user for a new time, then use sprkly_update_scheduled_post. A posted post comes back as posted (it only shows again), a failed post stays failed, and a draft stays a draft. Only when the user asks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_id": "<post_id>"
    },
    "name": "sprkly_restore_from_bin"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe id of the post in the Bin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses outcome-by-state behavior that annotations cannot express: scheduled posts in the past or within 2 minutes return as drafts (never auto-publishing), posted returns posted, failed stays failed, draft stays draft. This is exactly the non-obvious behavioral context an agent needs, and it is consistent with idempotentHint=true and destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, then constraints, then state outcomes, then the permission gate. It is dense but nearly every clause carries distinct information; the state-transition list is long but is the tool's core semantics rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single-parameter, non-destructive mutation with no output schema, the description covers eligibility window, state-dependent results, the auto-publish hazard, and the correct follow-up tool. Nothing an agent needs in order to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter, and schema coverage is 100% with 'The id of the post in the Bin' already documented. The description's 30-day Bin constraint narrows which post_ids are valid but does not add format or sourcing guidance beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Bring a deleted post back from the Bin') and immediately differentiates itself from the nearby mutation tools by naming the follow-up tool sprkly_update_scheduled_post. An agent can tell this apart from sprkly_delete_scheduled_post or sprkly_draft_post without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit eligibility conditions (only posts in the Bin, within 30 days of deletion), an explicit permission gate ('Only when the user asks'), and a routing rule to sprkly_update_scheduled_post when a new time is needed. When-to-use and when-to-hand-off are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All sprkly-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources