Skip to main content
Glama

asksteps

by co.asksteps

asksteps: publish a form, or get the link to publish it

asksteps_publish_form
Idempotent

Publishes a form or funnel — or, when the account has not authorised an agent to publish, returns the link where the user does it themselves. Requires "publish:write". Read the status: "confirmation_required" means NOTHING happened and you should hand over the url; "input_required" means you must ask the user for the fields listed in "missing" and call again; "published" means it is live at the returned url. NEVER invent a slug — it becomes a public address that stays in circulation. Ask the user. Publishing puts the form on the open internet, with the legal obligations that come with a public page; say so before you ask. Taking a form offline (publish = false) always works and needs no mandate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoThe path the form should live at, e.g. "kontakt". Ask the user; never make one up.
targetNoWhere to publish: "page" (a page on the asksteps platform, the usual choice) or "whitelabel" (the customer's own subdomain or domain). Defaults to "page".
confirmNoSet to true only AFTER the user has explicitly agreed. Without it nothing is switched.
form_idYesThe form or funnel id.
publishNotrue to publish (default), false to take it offline again.
visibilityNoWho may find it: "public" (listed and indexable), "unlisted" (only via the link) or "password". Ask the user.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoThe public address of the form once it is live, or the link where the user confirms the publication themselves.
noteYesOne sentence for the user. On "confirmation_required" make clear that nothing has been published yet.
statusYesOutcome. One of: "published" (it is live now), "unpublished" (taken offline), "input_required" (the mandate is there but something is missing — see missing), "confirmation_required" (no mandate: give the user the url and let them do it), "not_connected", "not_found", "not_allowed" (the mandate does not cover this channel), "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.
targetNoThe channel this answer is about: "page" (a page on the asksteps platform) or "whitelabel" (the customer's own subdomain or domain).
missingNoThe parameters you still have to supply, by name. Ask the user for each of them and call again with all of them plus confirm = true. Never invent a slug — it becomes a public address that stays in circulation.

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: the 'publish:write' requirement, the meaning of statuses, the warning never to invent slugs, the legal implications of publishing publicly, and the unconditional behavior of publish=false. No contradiction with the idempotentHint=true annotation is present.

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

Conciseness5/5

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

The description is dense but every sentence earns its place, covering purpose, status handling, agent guidance, and warnings. It is front-loaded with the core publish-or-return-link behavior, then systematically adds necessary guardrails without padding.

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?

Even with a rich schema and annotations, the description covers all critical operational details: authorization failure, statuses, required user interaction, slug safety, legal notice, and offline behavior. An agent has enough to call the tool correctly across the main scenarios.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful guidance on top: 'never make one up' for slug, 'Set to true only AFTER the user has explicitly agreed' for confirm, and repeated emphasis to ask the user. This elevates the value beyond the schema alone.

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 and resource ('Publishes a form or funnel') and immediately differentiates the alternate outcome when the account lacks authorization. This clearly distinguishes the tool's purpose from siblings like asksteps_update_publication.

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?

Provides explicit conditional guidance: what to do on 'confirmation_required', 'input_required', and 'published' statuses, and notes that taking offline always works without mandate. It does not explicitly name alternative sibling tools for comparison, but the conditional workflow is strong enough context.

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

All asksteps toolsInspect
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