asksteps

asksteps: read one funnel with its branching

asksteps_get_funnel

Read-onlyIdempotent

Reads one funnel of the connected asksteps account: its questions, answers and where each answer leads. Requires "forms:read". ALWAYS call this before asksteps_update_funnel — the write replaces every question, so you need the current state to keep what you are not changing. If the id turns out to be a flat form, the answer says so and points you at asksteps_get_form.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`funnel_id`	Yes	The funnel id, as returned by asksteps_list_forms.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	The name of the funnel as the customer sees it in their account.
`note`	Yes	One sentence for the user, explaining the outcome and what to do next.
`spec`	No	The structure of the funnel, in the same shape asksteps_update_funnel expects.
`status`	Yes	Outcome. One of: "ok", "not_connected", "not_found", "not_a_funnel" (this is a flat form — use asksteps_get_form instead), "error". Authorisation can also refuse before the tool runs: "plan_required" (the account's plan does not include agent access), "not_enabled" (the account owner has not switched agent access on), "owner_required" (only the account owner may do this), "mandate_required" (the owner has not granted a mandate for this). The note then says what the user has to do.
`editable`	No	Whether asksteps_update_funnel may write this funnel back. When false, DO NOT try — it contains things this format cannot describe, and writing would delete them.
`funnelId`	No	The id of the funnel, to pass back to asksteps_update_funnel.
`blockedBy`	No	Why writing is blocked, in one sentence. Empty when editable.
`themeCustomized`	No	True when the funnel uses a hand-built design instead of one of the presets.
`screensBlockedBy`	No	Why the intro/success/dismiss pages must not be sent back. Empty when they may be.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false. The description adds the prerequisite forms:read scope, the branching behavior, and the flat-form fallback behavior. It aligns with annotations and adds useful context beyond them.

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 description is compact, front-loads the main purpose, and the guidance about the write replacement is placed prominently. Some redundancy with the title exists, but each sentence earns its place.

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?

The tool has one required parameter fully documented, strong read-only annotations, an output schema exists, and the description covers the fallback to asksteps_get_form. Nothing an agent needs to call it correctly is missing.

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% and the one parameter is clearly described as the funnel id from asksteps_list_forms. The description doesn't add much beyond the schema, but there is little need. Inline schema descriptions are complete so baseline 3 is appropriate.

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 title and description clearly state the tool reads one funnel and its branching (questions, answers, where each answer leads). It distinguishes from the sibling asksteps_get_form by noting that if the id is a flat form the response says so and points to the correct tool.

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?

Explicitly instructs to ALWAYS call this before asksteps_update_funnel because the write replaces every question, and explains how to handle the case where the id is a flat form by pointing to asksteps_get_form. This is strong when-to-use and alternative guidance.

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

All asksteps tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Tools are mostly distinct with clear ownership of each resource and action, and descriptions explicitly contrast sibling pairs (analyze_pdf vs import_pdf, create_form vs create_funnel, publish_form vs update_publication, change_plan vs start_checkout). However, an agent skimming names alone could misselect between the four creation tools or the two PDF tools without reading the descriptions carefully.

Naming Consistency5/5

Every tool follows the asksteps_<verb>_<noun> pattern perfectly, with uniform verbs like get_, list_, create_, and update_. The only slight deviation is create_from_template, but even that stays predictable and readable within the convention.

Tool Count3/5

At 24 tools, this sits at the heavy end of the 16-25 borderline range. The broad domain (form/funnel building, publishing, PDF import, billing, stats, leads) justifies most of them and there is no obvious redundancy, but the sheer volume makes navigation harder than a tighter set.

Completeness4/5

The core form and funnel lifecycle is well covered: multiple creation paths, read, full replacement update, delete with confirmation, publish/unpublish, stats, and leads export. Billing covers first purchase, plan changes, and quota checks. Minor gaps exist — no dedicated subdomain listing tool, no funnel-specific stats, and no programmatic PDF field mapping — but these are explicitly documented as human steps, so agents can work around them.

Resources

Need Help?