Skip to main content
Glama
YawLabs

fetch-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

http_delete

DestructiveIdempotent

Send an HTTP DELETE request to a target URL, with support for custom headers, body, authentication, and retries. Handles idempotent deletion semantics per HTTP spec.

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_msNoTimeout in ms for each attempt, covering DNS, every redirect hop and the body (default 10000, max 120000). Retries get a fresh budget; a whole call is capped at 5 minutes.
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 loopback / private / link-local targets for this call (default false). Refused unless the server operator launched fetch-mcp with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 -- SSRF protection stays on by default either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • changedInput schema / properties / allow_private_hosts / description
      Previous value: -"Allow requests to loopback / private / link-local addresses. SSRF protection is on by default — only flip this when intentionally talking to localhost."New value: +"Allow loopback / private / link-local targets for this call (default false). Refused unless the server operator launched fetch-mcp with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 -- SSRF protection stays on by default either way."
    • changedInput schema / properties / timeout_ms / description
      Previous value: -"Request timeout in ms (default 10000, max 120000)"New value: +"Timeout in ms for each attempt, covering DNS, every redirect hop and the body (default 10000, max 120000). Retries get a fresh budget; a whole call is capped at 5 minutes."
  2. First observedv0.6.1

TDQS

A3.7/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. The description adds the specific behavioral note that repeated DELETEs typically return 404/410, which is not covered by annotations. This is useful additional context beyond the structured fields.

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 a single sentence, front-loaded with the core operation and a relevant behavioral note. No filler or redundancy. It 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?

The description is minimal, covering the core operation and idempotency, but does not mention return format, error handling, or response structure. However, since no output schema exists and the tool is an HTTP client, the expected behavior (status code, body) is standard. The description is adequate but could be enriched with a note about the response.

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, which is acceptable given the high schema coverage. 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?

The description clearly states the operation: 'Perform an HTTP DELETE.' This identifies the specific verb and resource (an HTTP endpoint), which differentiates it from sibling tools like http_get, http_put, etc. It also mentions idempotency, adding useful semantic context.

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

Usage Guidelines2/5

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

No explicit guidance on when to use DELETE vs. other HTTP verbs or alternatives. The intent is implied by the method name and the general HTTP semantics, but the description does not state any conditions, exclusions, or alternatives. With many sibling HTTP tools, explicit routing would be helpful.

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