Skip to main content
Glama

redirect_add

Add a redirect rule mapping a source path to a destination path, with configurable HTTP status codes (301, 302, 307, 410). Supports regex patterns and inactive 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 indicate non-readOnly, non-destructive, non-idempotent. Description adds behavioral context: 410's destination is meaningless, rule can be disabled, regex pattern support. No contradictions.

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?

Three succinct sentences: main action, defaults/allowed values, edge cases. No wasted words, front-loaded purpose.

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?

Covers key behaviors and edge cases. No output schema, so return values not needed. Could mention prerequisites (e.g., site must exist) but schema already provides source hint.

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?

All 6 parameters have schema descriptions (100% coverage), and description adds extra meaning: explains 410's effect on destination, active=false to disable, regexp as pattern flag. Adds value beyond schema.

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' with specific verb+resource. It distinguishes from sibling tools like redirect_delete, redirect_update, redirects_list.

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?

Provides clear guidance on parameter usage (e.g., 410 case, defaults, regexp). Does not explicitly contrast with alternatives, but sibling tools have distinct purposes.

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