Skip to main content
Glama

Create Redirect

create_redirect
Destructive

Create a new seliee_redirect (starts as UNPUBLISH, or PUBLISH with publish=True) on the website given by seliee_website_id or seliee_website_uuid. Returns seliee_redirect_id and seliee_redirect_uuid.

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": {
      "seliee_redirect_title": "<seliee_redirect_title>"
    },
    "name": "create_redirect"
  }
}

Input Schema

NameRequiredDescriptionDefault
publishNo
seliee_website_idNo
seliee_redirect_urlNo
seliee_redirect_utmNo
seliee_website_uuidNo
seliee_redirect_modeNoSLUG
seliee_redirect_pathNo
seliee_redirect_slugNo
seliee_redirect_titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / publish
      Added value: +{
      +  "default": false,
      +  "title": "Publish",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds genuine context beyond that: the new redirect begins in UNPUBLISH state unless publish=True, and it returns the created IDs. It does not explain why a create is flagged destructive, whether duplicate slugs/URLs will error, or what happens if the target website is invalid.

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?

Two tight sentences with no filler; the publish-state behaviour is front-loaded and the return values are stated last. Parameter names are anchored with backticks, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter creation tool with zero schema description coverage and no output schema, the description is thin: it omits the single required parameter and the mode/path/slug targeting fields that determine where the redirect resolves. The return-value note is helpful, but an agent could not confidently fill in this schema from the description alone.

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

Parameters2/5

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

Schema description coverage is 0% across 9 parameters, so the description must carry the load, and it only explains three: publish, website id, and website uuid. It says nothing about the required seliee_redirect_title, nor about redirect_url, redirect_utm, redirect_mode (which defaults to 'SLUG' with no explanation), redirect_path, or redirect_slug — leaving the slug-versus-path distinction entirely undocumented.

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 ('Create a new seliee_redirect') plus the parent scope (the website given by id or uuid). It does not explicitly distinguish itself from siblings such as edit_redirect, publish_redirect, or create_page, but the resource is named precisely enough to separate it from the page/article creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by explaining the publish=True flag for immediate publication versus the default UNPUBLISH starting state, which hints at the create-then-publish workflow. It never states when to use this over edit_redirect or publish_redirect, nor does it state prerequisites such as needing an existing website.

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.