Skip to main content
Glama
Sign In

GrowthDept

by app.growthdept
OverviewDiscussionsAdmin

Take a hosted page down

take_page_down
DestructiveIdempotent

Take one of the pages GrowthDept hosts off the internet. Its address then says it is no longer available. Nothing is deleted and put_page_back restores it. Only call this when the person asked for this page to come down.

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": {
      "content_piece_id": "<content_piece_id>",
      "person_asked": "<person_asked>"
    },
    "name": "take_page_down"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_askedYesSet true only when the person asked, in this conversation, for this exact item to be decided. Never set it on your own judgement.
content_piece_idYesThe page's id from hosted_pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is largely covered. The description adds real value by disclosing reversibility ('Nothing is deleted and put_page_back restores it') and the user-visible outcome on the URL, which is context the annotations cannot express. It stops short of noting any propagation delay or permission requirements, so a 3 rather than higher.

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?

Four short sentences, front-loaded with what happens to the page, then reversibility, then the call condition. No redundant restatement of the title and no filler.

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?

A simple two-parameter, non-open-world tool with full annotation coverage and no output schema; the description covers the effect, reversibility, and the usage gate. Nothing an agent needs in order to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the schema already explains both fields thoroughly, so the baseline is 3. The description earns an extra point by reinforcing the intent of the person_asked gate with consequence framing ('this page to come down'), making clear it should not be set on the agent's own judgement.

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?

States a specific verb and resource ('Take one of the pages GrowthDept hosts off the internet') plus the observable effect on the page's address, and implicitly distinguishes it from the inverse sibling put_page_back. An agent can tell what this does and what it is not (a deletion) without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ('Only call this when the person asked for this page to come down'), names the inverse operation (put_page_back) that undoes it, and rules out misuse by clarifying nothing is deleted. This is close to a complete when/when-not/alternative statement.

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

All GrowthDept toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources