Skip to main content
Glama

rowfeed/redirect-checker

rowfeed--redirect-checker
Destructive

This tool calls the Actor "rowfeed/redirect-checker" and retrieves its output results. Actor description: Check thousands of URLs: HTTP status, every redirect hop, final URL, 301 or 302, redirect loops, dead links and response time. For SEO migrations and link audits. $0.10 per 1,000 URLs, invalid addresses free.

Input Schema

NameRequiredDescriptionDefault
urlsNoThe addresses to check, up to 50,000 per run. Without http:// or https://, https:// is used. Example values: ["http://apify.com","https://apify.com/store","https://www.iana.org/domains/example"]
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
onlyProblemsNoLeave out addresses that answer 200 directly. Only delivered rows are charged.

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  2. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  3. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  4. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  5. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  6. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  7. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  8. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  9. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  10. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  11. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  12. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  13. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  14. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  15. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  16. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  17. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "null",
      -  "string"
      -]New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "null",
      -  "number"
      -]New value: +[
      +  "number",
      +  "null"
      +]
  18. Changed3 schema fields changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / final_url / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "null",
      +  "string"
      +]
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / status / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +[
      +  "null",
      +  "number"
      +]
  19. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the cost model ($0.10 per 1,000 URLs, invalid addresses free), the throughput scale (thousands of URLs), and exactly what is measured per URL. That is real behavioral context. It never explains the destructiveHint=true / readOnlyHint=false profile (i.e., that a run is created in the account), so the annotation picture is not fully reconciled.

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?

Two sentences, front-loaded with what the tool does and followed by capability, use case, and price. The opening 'calls the Actor ... and retrieves its output results' is boilerplate wrapper text but it is short and the rest earns its place.

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 an output schema present and full parameter documentation, the description need not explain return values; adding cost and coverage limits completes the operational picture. The remaining gap is sibling differentiation against the family's other link and redirect tools.

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%; every parameter including urls, waitSecs (0–45 cap, nextStep polling, fire-and-forget at 0), and onlyProblems is already documented in the schema. The description adds no parameter-level meaning, so baseline 3 applies.

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?

The description states a concrete verb and resource: it calls the rowfeed/redirect-checker Actor and checks thousands of URLs for HTTP status, every redirect hop, final URL, 301/302, loops, dead links, and response time. That is far more specific than a name restatement. It does not, however, say how this differs from close siblings such as rowfeed--broken-link-checker or rowfeed--backlink-checker, so it stops short of a 5.

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 phrase 'For SEO migrations and link audits' implies when the tool is appropriate, and the schema-level note about up to 50,000 URLs clarifies scale. But there is no explicit when-not guidance and no named alternative among the overlapping link/redirect checking siblings, leaving the agent to infer which checker to pick.

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.