Skip to main content
Glama

Create schedule

create_schedule
Destructive

Schedule a saved query to run on a cron cadence and deliver its result to exactly one destination: a Google Sheets tab or a Slack channel. Use it when the user wants a report refreshed or posted regularly; for a one-off file use export_query_results. Save the SQL first with save_query if it is not in the library, and check list_schedules, since each saved query can have only one schedule. Every run replaces what the previous run wrote to the sheet range, or posts a new Slack message. Set spreadsheetId, or createNew with spreadsheetName, or slackChannelId, never more than one destination. Requires a plan that includes scheduling, the write and execute scopes, and a member role that can edit. The query must be one you could run yourself: shared with the team on an approved_queries connection, and a read unless the connection's aiAccess is same_as_people. Test it right away with run_schedule_now.

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": {
      "savedQueryId": "<savedQueryId>",
      "cronExpression": "<cronExpression>"
    },
    "name": "create_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneNoIANA timezone. Defaults to UTC.
createNewNoCreate a new spreadsheet named spreadsheetName.
sheetNameNoTab to write to.
startCellNoA1 notation. Defaults to A1.
savedQueryIdYesSaved query id from list_queries.
spreadsheetIdNoExisting spreadsheet to write to. Omit and set createNew with spreadsheetName to make a new one.
cronExpressionYes5-field cron expression, e.g. '0 9 * * 1' for Monday 9am.
includeHeadersNoWrite column names as the first row. Defaults to true.
slackChannelIdNoSlack channel to post to, instead of a spreadsheet.
spreadsheetNameNoName for a new spreadsheet when createNew is true.
slackChannelNameNoDisplay name of the Slack channel.
slackMessageTemplateNoMessage template for Slack. Omit to post the raw result.

Output Schema

NameRequiredDescriptionDefault
scheduleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true; the description explains precisely what that destruction means: every run replaces what the previous run wrote to the sheet range, while Slack runs post a new message. It goes further with gating context the annotations cannot express — a scheduling-enabled plan, write and execute scopes, an edit-capable member role, and query eligibility rules (approved_queries connection, read unless aiAccess is same_as_people).

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?

It is a dense single paragraph, but information is front-loaded: purpose and destination model first, then alternatives, prerequisites, overwrite semantics, constraints, permissions, and testing. No sentence is filler, though the volume of prerequisite and permission rules in one undifferentiated block makes it slightly harder to scan than a bulleted structure would be.

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?

For a 12-parameter mutation tool with real permission gates, the description covers purpose, alternatives, prerequisites, cross-parameter constraints, destructive run semantics, and authorization requirements; the output schema covers return values and the schema covers every parameter. An agent has everything needed to call this correctly, with run_schedule_now pointed to for verification.

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%, so the baseline is 3; the description earns above baseline by stating the mutual-exclusion rule across three destination modes (spreadsheetId, createNew with spreadsheetName, slackChannelId) with 'never more than one destination', a cross-parameter constraint the schema cannot express. It does not add detail on cron syntax, timezone, or the Slack template beyond what each property already 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?

The first sentence gives a specific verb (schedule a saved query), the trigger mechanism (cron cadence), and the delivery constraint (exactly one destination: Google Sheets tab or Slack channel). It explicitly distinguishes itself from export_query_results (one-off file) and run_schedule_now (immediate test), so an agent can route correctly without inspecting schemas.

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?

It names the affirmative use case ('when the user wants a report refreshed or posted regularly') and two alternatives with their selecting conditions. It also states the prerequisite chain — save_query first, check list_schedules because each saved query can have only one schedule — which prevents a predictable duplicate-schedule failure.

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