Skip to main content
Glama
YawLabs

fetch-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

http_delete

DestructiveIdempotent

Perform HTTP DELETE requests to remove resources from a target URL. Supports custom headers, authentication, retries, and response size limits for controlled deletion operations.

Instructions

Perform an HTTP DELETE. Idempotent (per spec): a repeated DELETE on an already-deleted resource typically returns 404/410.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTarget URL (http:// or https://)
bodyNoRaw request body as a string
headersNoExtra request headers as a key/value object
retriesNoRetries on 408/425/429/500/502/503/504 with exponential backoff (default 0)
body_jsonNoRequest body as a JSON value — sets content-type to application/json if none given
max_bytesNoMax response body size in bytes before the body is truncated (default 5MiB, ceiling 100MiB)
basic_authNoHTTP Basic auth credentials
timeout_msNoRequest timeout in ms (default 10000, max 120000)
user_agentNoUser-Agent override (default identifies as @yawlabs/fetch-mcp)
decode_textNoForce text decoding (true) or binary base64 (false). Defaults to auto — text for text/*, json, xml, etc; binary otherwise.
bearer_tokenNoBearer token sent as Authorization: Bearer <token>
content_typeNoContent-Type header to send with the body (e.g. application/json, text/plain, application/x-www-form-urlencoded)
max_redirectsNoMax redirect hops to follow (default 5)
allow_private_hostsNoAllow requests to loopback / private / link-local addresses. SSRF protection is on by default — only flip this when intentionally talking to localhost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, and the description adds a concrete behavioral detail (repeated DELETE typically returns 404/410). This goes beyond the annotations by explaining the outcome of a specific edge case, providing useful context without contradiction.

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?

Two sentences with zero redundancy: the main purpose is front-loaded, and the idempotency note is concise and informative. Every word earns its place.

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

Completeness3/5

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

For a tool with 14 parameters and no output schema, the description is minimal. It covers the core operation and idempotency, but omits any guidance on response handling, error cases, or when to choose DELETE over alternatives. The schema carries most of the burden, so this is adequate but not complete.

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 description coverage is 100%, so the schema fully documents all 14 parameters. The description adds no parameter-specific meaning beyond the schema's own descriptions, which sets the baseline at 3 as expected.

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 states a specific verb ('Perform') and resource ('HTTP DELETE'), clearly distinguishing it from sibling methods like http_get or http_post. It also adds a key semantic detail about idempotency, so an agent knows exactly what this tool does.

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?

The description does not explicitly state when to use DELETE vs other HTTP methods, relying on the method name to convey intent. It lacks contrast with siblings or any scenario guidance, so an agent must infer usage from HTTP semantics alone.

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

Deploy Server

Other Tools