Skip to main content
Glama

Domain-Weiterleitungen anzeigen

get_domain_redirects
Read-only

Listet die Domain-Weiterleitungen, die auf eine Domain zeigen — welche andere Domain also auf diese hier weiterleitet, mit Kennung und mit dem, was daran hängt. Das lesende Gegenstück zu redirect_domain und die Voraussetzung für remove_domain_redirect. Anzugeben ist die Domain MIT dem Hosting, also das ZIEL der Weiterleitung (bei "alte-domain.de leitet auf neue-domain.de" ist das neue-domain.de). Je Eintrag steht dabei, ob über die weiterleitende Domain nur Web-Aufrufe laufen oder auch E-MAIL an dieselben Postfächer — Letzteres ist der Standard beim Einrichten und geht beim Aufheben mit verloren; das gehört in jede Antwort an den Kunden. Eine leere Liste ist eine abgerufene Auskunft ("es leitet keine Domain hierher"); war die Liste dagegen nicht abrufbar, meldet die Antwort das ausdrücklich als Messausfall — daraus darf NIE "es gibt keine Weiterleitung" werden. STAGING-KOPIEN erscheinen im Hosting-System als dieselbe Art Eintrag und werden deshalb mitgelistet, aber ausdrücklich als Staging gekennzeichnet: Das sind Testumgebungen, keine vom Kunden eingerichteten Weiterleitungen, und remove_domain_redirect hebt sie nicht auf. Unterschieden wird am Namen; ein Feld, das beides sicher trennt, gibt es nicht — bei Unklarheit nicht raten.

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": {
      "domain": "<domain>"
    },
    "name": "get_domain_redirects"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDie Domain MIT dem Hosting, also das Ziel der Weiterleitung, z. B. neue-domain.de

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds substantial behavioral context beyond that — entries carry a web-only vs. also-EMAIL scope flag (email is the default and is lost on removal), staging copies are included but marked and are NOT removable by remove_domain_redirect, and an empty result is a valid answer while a failed fetch is reported as a measurement failure that must never be read as 'no redirects'. That failure-semantics warning is exactly the kind of non-obvious behavior annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the read/write relationship, then the parameter meaning, then return content, then the failure and staging caveats — a logical progression. It is dense and slightly repetitive (the staging point is restated across two sentences), but given the traps it must convey, most sentences earn their place.

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?

There is no output schema, and the description compensates by describing what each entry contains (identifier, what depends on it, web vs. email scope, staging marking) plus the empty-result vs. failure distinction. For a single-parameter read tool with annotations covering safety, nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the schema already defines the single 'domain' parameter as the redirect target, so the baseline is 3. The description goes further by spelling out the direction with a worked example and stressing 'MIT dem Hosting', which resolves a genuine ambiguity for the caller rather than merely restating the 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 states a specific verb+resource (listing domain redirects pointing at a given domain) and immediately disambiguates the direction — it lists domains that redirect TO the given one, not the other way round. It also names its siblings (redirect_domain, remove_domain_redirect) and positions itself relative to them, so an agent can distinguish it without opening another schema.

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

Usage Guidelines5/5

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

Explicitly frames itself as the read counterpart to redirect_domain and the prerequisite for remove_domain_redirect, and tells the caller exactly which value to pass (the redirect TARGET, with a concrete 'alte-domain.de → neue-domain.de' example). It also warns not to guess when staging vs. customer redirects are ambiguous — clear when-to-use and when-to-be-cautious guidance.

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