appforshare-mcp

Official

by appforshare

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Delete a build

delete_build

DestructiveIdempotent

Permanently removes a build and disables its install link immediately; restorable from the dashboard for 7 days. Requires developer role and explicit confirm: true.

Instructions

Delete a build. Its install link stops working at once; it can be restored from the dashboard for 7 days. Ask the person first and pass confirm: true. Developer role.

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": {
      "build": "<build>",
      "confirm": "<confirm>"
    },
    "name": "delete_build"
  }
}

Input Schema

Name	Required	Description	Default
`build`	Yes	Build id or the slug of its install link
`confirm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.7Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds genuinely new context: the install link breaks instantly and the build is recoverable from the dashboard for 7 days. The Developer-role requirement is also disclosed. Minor gap: nothing is said about what happens to installs or feedback attached to the build.

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?

Four short sentences, front-loaded with the action, then consequences, then the safety step. Every sentence carries information; no filler. Could be marginally tighter by folding the role requirement into the confirmation sentence.

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

Completeness4/5

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

For a two-parameter destructive tool with no output schema, the description covers effect, reversibility window, required confirmation, and authorization. The main omission is post-deletion side effects on related resources, but that is secondary for correct invocation.

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

Parameters5/5

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

Schema coverage is only 50% (the 'build' property is described, 'confirm' only carries const: true). The description compensates by explaining that confirm: true is a deliberate confirmation gate tied to asking the person first, which is meaning the schema cannot convey. It also reinforces that 'build' may be an id or an install-link slug.

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

Purpose4/5

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

States a specific verb and resource ('Delete a build') and immediately clarifies the scope of the effect (the install link stops working). It does not explicitly distinguish itself from the sibling retire_build, so an agent must infer the difference, but the core purpose is unambiguous.

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

Usage Guidelines3/5

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

Gives a real precondition workflow ('Ask the person first and pass confirm: true') and an access requirement ('Developer role'), which is more than most delete tools. However, it never says when to choose this over retire_build or remove_build_link, which are the closest alternatives an agent would weigh.

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