mcp-server

Scrape Schedules

alterlab_schedule

Destructive

Manage recurring scrape schedules. action=create runs a scrape of one or more URLs on a cron expression; action=list returns your schedules; action=delete removes one by schedule_id (it stops triggering). Every run spends credits like a scrape; minimum intervals depend on your balance tier.

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": {
      "action": "<action>"
    },
    "name": "alterlab_schedule"
  }
}

Input Schema

Name	Required	Description
`cron`	No	create: five-field cron expression, e.g. '0 9 * * *'
`name`	No	create: schedule name
`urls`	No	create: URLs to scrape on each run
`limit`	No	Page size (default 20)
`action`	Yes	create, list or delete
`offset`	No	Items to skip
`formats`	No	create: output formats
`timezone`	No	create: timezone for the cron expression (default UTC)
`active_only`	No	list: only active items
`schedule_id`	No	delete: schedule id from create or list
`webhook_url`	No	create: HTTPS endpoint that receives results

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructive, non-idempotent, open-world behavior; the description adds real value beyond them by disclosing that every run consumes credits like a scrape, that minimum intervals are tier-dependent, and that deletion stops future triggering rather than deleting results.

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 the purpose, then a compact action-by-action breakdown with no filler. Sentences are somewhat long but every clause carries information an agent needs.

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

Completeness3/5

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

For an 11-parameter action-dispatch tool with no output schema, the description covers all three action modes and cost behavior, but leaves the list return shape, pagination semantics, and the meaning of formats/webhook beyond the schema's terse labels unaddressed.

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 each parameter already labels which action it applies to, so the schema carries the load. The description reinforces the action/schedule_id relationship but adds no format, default, or constraint detail beyond what the schema documents.

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?

States a specific verb and resource ("Manage recurring scrape schedules") and then enumerates the three actions with their effects, so an agent can distinguish it from one-off siblings like alterlab_scrape or alterlab_batch_scrape without opening the schema.

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 each action (create runs scrapes on a cron, list returns schedules, delete removes one and stops triggering) and notes the balance-tier constraint on minimum intervals, but never names an alternative tool or says when not to schedule versus scraping ad hoc.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.