mcp

create_backup_schedule

Create a Firestore backup schedule.

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": {
      "parent": "<parent>",
      "backupSchedule": "<backupSchedule>"
    },
    "name": "create_backup_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`parent`	Yes	Required. The parent database. Format `projects/{project}/databases/{database}`
`backupSchedule`	Yes	Required. The backup schedule to create.

Output Schema

Name	Required	Description
`name`	No	Output only. The unique backup schedule identifier across all locations and databases for the given project. This will be auto-assigned. Format is `projects/{project}/databases/{database}/backupSchedules/{backup_schedule}`
`retention`	No	At what relative time in the future, compared to its creation time, the backup should be deleted, e.g. keep backups for 7 days. The maximum supported retention period is 14 weeks.
`createTime`	No	Output only. The timestamp at which this backup schedule was created and effective since. No backups will be created for this schedule before this time.
`updateTime`	No	Output only. The timestamp at which this backup schedule was most recently updated. When a backup schedule is first created, this is the same as create_time.
`dailyRecurrence`	No	For a schedule that runs daily. Only one of this field or weeklyRecurrence should be set.
`weeklyRecurrence`	No	For a schedule that runs weekly on a specific day. Only one of this field or dailyRecurrence should be set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026

changedInput schema / $defs / BackupSchedule / properties / dailyRecurrence / description

Previous value: -"For a schedule that runs daily."New value: +"For a schedule that runs daily. Only one of this field or weeklyRecurrence should be set."

changedInput schema / $defs / BackupSchedule / properties / weeklyRecurrence / description

Previous value: -"For a schedule that runs weekly on a specific day."New value: +"For a schedule that runs weekly on a specific day. Only one of this field or dailyRecurrence should be set."

changedOutput schema / properties / dailyRecurrence / description

Previous value: -"For a schedule that runs daily."New value: +"For a schedule that runs daily. Only one of this field or weeklyRecurrence should be set."

changedOutput schema / properties / weeklyRecurrence / description

Previous value: -"For a schedule that runs weekly on a specific day."New value: +"For a schedule that runs weekly on a specific day. Only one of this field or dailyRecurrence should be set."

AddedAug 19, 2026
RemovedAug 19, 2026
AddedAug 19, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows it is a non-destructive write to a closed API. The description adds nothing beyond that — notably it omits that the created schedule will begin producing automatic backups, which is a meaningful side effect, and it says nothing about required permissions or limits (e.g. one schedule per database).

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

Conciseness3/5

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

A single short sentence is efficient but under-specified for a mutation tool; the brevity saves space at the cost of any useful context. Not wasteful, but also not earning its place with any added value.

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?

An output schema exists and the input schema is richly described, which lowers the burden. However, for a write tool that creates an ongoing recurring job, the description gives no indication of consequences or constraints, leaving the agent reliant entirely on structured fields.

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 coverage is 100%, so parent and backupSchedule fields are fully documented in the schema, including mutually exclusive dailyRecurrence/weeklyRecurrence and the 14-week retention cap. The description adds no additional parameter 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?

States a specific verb and resource ("Create a Firestore backup schedule"), which distinguishes it from siblings like create_database or update_backup_schedule. It does not, however, differentiate from other create_* operations beyond the resource name.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives or when this is preferable to reusing an existing schedule. The agent must infer usage from the name alone.

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

All mcp 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.

Resources

Need Help?