@dropthis/mcp

Official

by dropthis-dev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

List a drop's deployments

dropthis_list_deployments

Read-only

List a drop's past deployments and revisions, newest first. Use to view content history, compare versions, or revert to an earlier iteration.

Instructions

List a drop's content history — its past versions / revisions / deployments, newest first. Use when the user asks for the content history, previous versions, or revisions of a drop. Requires drop_id (the drop_… id, not the slug or URL).

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": {
      "drop_id": "<drop_id>"
    },
    "name": "dropthis_list_deployments"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max items (default 20).
`cursor`	No	Pagination cursor from a previous call.
`drop_id`	Yes	The `drop_…` id of the drop whose deployments to list (id-only — a URL or slug is rejected; call dropthis_resolve to turn a public URL/slug into its id first).

Output Schema

Name	Required	Description	Default
`items`	No	The page of deployments.
`nextCursor`	No	Cursor for the next page; null/absent at the end.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.0Aug 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds that results are newest first and requires the drop_… id, not the slug/URL. This is useful behavioral context beyond the annotations, though it doesn't mention pagination (but cursor is in schema).

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 two sentences, front-loaded with the purpose and ends with a required-id note. Every sentence earns its place.

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?

Given the readOnly annotation, the output schema, and full parameter schema coverage, the description is sufficiently complete. It covers ordering, when to use, and the id format requirement.

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?

The schema has 100% coverage with detailed descriptions for all three parameters, so the description adds no new parameter semantics. It reinforces the drop_id format, but that's already in the schema, so it's redundant.

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 tool lists a drop's deployments/content history, using the verb 'list' and specifying the resource (deployments/versions). It also says 'newest first' and distinguishes it from restore (implicitly) by being a list operation.

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 description explicitly says 'Use when the user asks for the content history, previous versions, or revisions of a drop,' which is clear when-to-use guidance. It does not provide when-not-to-use or alternative tools, but the context is sufficient for choosing this over siblings like restore.

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