Skip to main content
Glama

List redirects

list_redirects
Read-onlyIdempotent

List redirects for a blog with search, status, type, and pagination filters. Requires manageBlog permission on the target blog. Blog-scoped API keys are supported.

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": {
      "blogId": "<blogId>"
    },
    "name": "list_redirects"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
typeNoFilter by HTTP status code.all
limitNoRedirects per page, from 1 to 100.
blogIdYesBlog ID. Use list_blogs to discover available blog IDs.
searchNoSearch source paths and destinations.
statusNoFilter by active state.all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds genuinely useful non-schema context: the required manageBlog permission and that blog-scoped API keys work, both of which affect whether a call will succeed. Return shape is left to the output schema, which is acceptable.

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 short sentences, front-loaded with the core action, then the filter axes, then the permission constraint. No sentence is redundant and nothing needed is pushed to the end.

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?

With annotations covering the safety profile, a 100%-documented schema, and an output schema defining return values, the description says everything an agent needs before calling. Only marginal gaps remain, such as ordering of results or whether an empty search returns all redirects.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter has an inline description including defaults, ranges, and enum values. The description's enumeration of 'search, status, type, and pagination filters' mirrors the schema without adding format or behavior detail (e.g., case sensitivity of search), so it lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List redirects for a blog') plus the filter axes (search, status, type, pagination), which cleanly separates it from create_redirect, get_redirect, and update_redirect. It stops short of explicitly naming those siblings, but the list/get/create distinction is unambiguous from the name and phrasing.

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?

Gives clear context for legitimate use: requires manageBlog permission on the target blog, and notes blog-scoped API keys are supported. It does not explicitly say when to prefer get_redirect over list_redirects (e.g., single known ID), so it falls just short of the top tier.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources