Skip to main content
Glama
Sign In

Pixelesq

by com.pixelesq
OverviewDiscussionsAdmin

Create redirect

create_redirect
Destructive

Create a URL redirect. Redirects have no draft: the rule applies on the live site without a publish, usually within minutes, and a source that matches a live page replaces that page for visitors. A source path can have only one active redirect (list_redirects shows the ones in use), and a redirect that leads back to its own source, directly or through other rules, is refused. A source of / (the home page) or a destination on another site needs confirm: true, sent only after the user agreed. If the answer was lost, check list_redirects for the source path before trying again.

Input Schema

NameRequiredDescriptionDefault
sourceYesSource URL path (e.g. /old-page)
confirmNoSet true only after the user confirmed replacing the home page or sending visitors to another site
permanentNoWhether this is a permanent (301) or temporary (302) redirect
projectIdYesThe project ID
descriptionNoDescription of why this redirect exists
destinationYesDestination URL path (e.g. /new-page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Set true only after the user confirmed replacing the home page or sending visitors to another site",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive and openWorld behavior, but the description adds substantial context: redirects go live without publishing, usually within minutes, can replace a live page, reject loops, and require confirmation in risky cases. It also covers retry behavior when the answer is lost.

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 front-loaded with the core action and then supplies only high-value behavioral constraints. Every sentence earns its place; there is no filler or repetition.

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?

For a destructive openWorld mutation with no output schema, it covers timing, side effects, uniqueness conflicts, loop refusal, confirmation requirements, and retry advice. Return shape is not described, but invocation requirements are complete.

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 description coverage is 100%, so the baseline is 3. The description adds useful semantics beyond the schema for source uniqueness and confirm conditions, though it does not explain the permanent or description parameters beyond what the schema already says.

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: 'Create a URL redirect.' It also names list_redirects for checking existing redirects, making it distinguishable from list/update/delete redirect siblings.

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?

Explains key use conditions and refusals: unique active source, no redirect loops, and confirm required for the home page or offsite destinations. It points to list_redirects after a lost answer, but does not explicitly route existing redirects to update_redirect.

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

All Pixelesq 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