Mark

Skip Setup Step

skip_setup_step

Idempotent

Skips one setup checklist row, or with skipped false brings it back, for everyone in the workspace, the same as Skip and Undo skip on Home's setup card. Use it when the user says they don't need a step. A done row stays done and is left as it is. Returns the updated rows, as get_setup_status does. step is one of: website, market, brand_voice, web_analytics, content_sources, social, buyer_questions, posting_times, connect_agent. Related: get_setup_status.

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": {
      "step": "<step>"
    },
    "name": "skip_setup_step"
  }
}

Input Schema

Name	Required	Description	Default
`step`	Yes	One of website, market, brand_voice, web_analytics, content_sources, social, buyer_questions, posting_times, connect_agent.
`skipped`	No	False brings a skipped row back.

Output Schema

Name	Required	Description	Default
`gaps`	Yes
`rows`	Yes
`ready`	Yes
`appUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations (idempotent, non-destructive, closed-world), the description discloses important behavioral traits the annotations cannot: the change applies to everyone in the workspace, a done row is left untouched, and the return mirrors get_setup_status. This is meaningful context for a mutation, though permission/auth requirements are still unstated.

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?

The definition is front-loaded with the core action and scope, and every sentence carries information (parity with UI, workspace scope, done-row behavior). The enum list plus the 'Related:' tag add slight redundancy with the schema, but overall it is tight.

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, the description needn't detail return values, and it correctly references get_setup_status instead. It covers scope, edge cases, and the sibling relation; the only remaining gap is authorization/prerequisite context for a workspace-wide mutation.

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 both parameters are already documented in the schema, including the default and the 'false brings a skipped row back' semantics. The description largely repeats the enum list and the skipped flag rather than adding format or syntax detail, so this meets the baseline of 3.

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 (skips) and resource (one setup checklist row), and clarifies the inverse behavior (with skipped false brings it back). It also names the sibling get_setup_status, so an agent can distinguish this from the read-only status tool without opening schemas.

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?

It gives a clear trigger ('Use it when the user says they don't need a step') and covers the reversal case, plus a 'Related: get_setup_status' pointer. It stops short of explicitly stating when NOT to use it or naming alternative mutation paths, so it is clear context rather than full exclusions.

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

All Mark 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?