Skip to main content
Glama

redirect_add

Add redirect rules to map old URLs to new ones, with support for permanent (301), temporary (302, 307) or gone (410) statuses. Optionally use regex patterns or create disabled rules.

Instructions

Add a redirect rule. source/destination are paths (e.g. /old → /new). redirect_type defaults to 301; allowed: 301, 302, 307, 410. Set regexp=true to treat source as a regex pattern. Set active=false to create the rule disabled. For 410 (Gone), destination is semantically meaningless — Voog still stores it but never redirects there; pass any value (e.g. source path).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite name from voog_list_sites
sourceYesSource path (e.g. /en/products/old)
destinationYesDestination path (e.g. /en/products/new). Ignored when redirect_type=410 (Gone) — 410 returns the status without redirecting.
redirect_typeNoHTTP status code: 301 (permanent), 302 (temporary), 307 (temporary, preserve method), 410 (gone — destination ignored). Default 301.
activeNoWhether the rule is active. Default true.
regexpNoIf true, treat 'source' as a regex pattern (Voog's regex redirect feature). Default false (literal path match).
Behavior4/5

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

Annotations are neutral (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds value by explaining that for 410, destination is ignored but still stored, and that defaults apply. No contradictions with annotations.

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 three sentences, each earning its place. It is front-loaded with the core purpose and follows with precise, essential details. No redundant or verbose language.

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 tool with 6 parameters (3 required, 1 enum) and no output schema, the description covers all essential behavioral aspects, parameter semantics, special cases, and defaults. It is complete without being overly long.

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

Parameters5/5

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

Schema coverage is 100%, yet the description adds significant extra context: examples (e.g., /old → /new), explanation of regexp and active flags, and clarification of 410 behavior. This goes beyond the schema's descriptions.

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 'Add a redirect rule' and explains the tool's verb and resource. It distinguishes from sibling tools like redirect_delete, redirects_list, and redirect_update by being the creation tool. The examples and parameter details reinforce its unique purpose.

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 provides clear context for using the tool, including parameter defaults and special behavior for 410. However, it does not explicitly contrast with alternatives (e.g., 'use redirect_update to modify existing rules'), which would make it a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runnel/voog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server