Skip to main content
Glama
Sign In
Spectre

Spectre

by pranrichh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_profile_banner

Remove your X/Twitter profile banner or header image immediately. Returns a confirmation JSON.

Instructions

⚠️ DESTRUCTIVE — Remove the profile banner/header image.

WARNING: This immediately removes your banner image.

Returns: Confirmation JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_profile_banner"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior4/5

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

Description includes a prominent warning about immediate removal ('DESTRUCTIVE') and states it returns a confirmation JSON. Since no annotations are provided, the description carries the full transparency burden and does so adequately, though it could mention irreversibility or side effects.

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?

Extremely concise: two sentences plus a warning. Front-loaded with the destructive nature. Every word adds value.

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 simple deletion tool with no parameters, the description covers purpose, behavior, and return format. Could mention idempotency or error handling, but overall sufficient.

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?

The tool has zero parameters, so the description does not need to explain any. The schema is fully covered by its emptiness, meeting the baseline of 4 for zero-parameter tools.

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 action: 'Remove the profile banner/header image.' It uses a specific verb and resource, distinguishing it from sibling tools like update_profile_banner.

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 guidance on when to use this tool versus alternatives (e.g., update_profile_banner). No mention of prerequisites or context such as needing to be authenticated.

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