Skip to main content
Glama
azickri

Repliz MCP Server

by azickri

Delete Scheduled Post

repliz_delete_schedule

Delete a scheduled post by providing its unique ID. Use this action to remove a scheduled post that is no longer needed.

Instructions

Delete a single scheduled post by id. Irreversible — confirm before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scheduleIdYesThe schedule id to delete.
Behavior4/5

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

With no annotations provided, the description carries the burden. It clearly states the tool is irreversible, which is a key behavioral trait. No other side effects or prerequisites are mentioned, but for a simple delete it's sufficient.

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

Conciseness5/5

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

The description is extremely concise: one sentence stating the action followed by a warning. No wasted words, front-loaded with purpose.

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?

For a single-parameter delete tool, the description is complete. It explains what it does, its irreversibility, and the parameter. No output schema is needed.

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?

Schema coverage is 100% with a clear description for 'scheduleId'. The tool description does not add any additional meaning beyond the schema's 'The schedule id to delete.' So baseline 3 is appropriate.

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?

The description clearly states the action 'Delete' and the resource 'single scheduled post by id'. It distinguishes itself from sibling 'repliz_delete_schedules' which likely deletes multiple.

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

Usage Guidelines4/5

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

The warning 'Irreversible — confirm before calling' provides a clear guideline to confirm before use. It implies caution but does not explicitly state when not to use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azickri/repliz-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server