delete_template
Delete a page template by providing its collective ID and template ID.
Instructions
Delete a page template.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| collectiveId | Yes | ||
| templateId | Yes |
Delete a page template by providing its collective ID and template ID.
Delete a page template.
| Name | Required | Description | Default |
|---|---|---|---|
| collectiveId | Yes | ||
| templateId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits such as reversibility or prerequisites. It only says 'Delete', which is insufficient for a potentially destructive action.
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 a single sentence with no fluff, but it is too minimal. It loses a point for lacking structure or front-loading critical details.
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 no output schema and low parameter coverage, the description fails to provide enough context for safe invocation, omitting required IDs and potential effects.
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 description coverage is 0%, so the description must explain parameters. It does not mention collectiveId or templateId, leaving the agent to rely solely on the schema without additional context.
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 the action (delete) and the resource (page template), distinguishing it from siblings like delete_page or delete_tag.
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?
No guidance on when to use this tool versus alternatives like delete_page or permanently_delete_collective. Missing context for appropriate invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/megamaced/nc_collectives-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server