Skip to main content
Glama
Sign In

Nas.com

by com.nas
OverviewDiscussionsAdmin

Unpublish Lead Form

unpublish_lead_form
Destructive

Unpublish a lead form. Requires confirm set to UNPUBLISH. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "formId": "<formId>"
    },
    "name": "unpublish_lead_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
formIdYesLead form ID, from a Nas.com lead form listing.
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
    • addedInput schema / properties / formId / description
      Added value: +"Lead form ID, from a Nas.com lead form listing."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already mark this as a destructive write. The description adds important behavioral context beyond annotations: permission gating, FREE-tier exclusion, grace-period warning handling, resubscribe link display, and blocked-access stopping conditions. It does not explain the form-state effect after unpublishing, but the added access-control behavior is substantial.

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 front-loaded with the action and then lists prerequisite checks in a logical order. There is some repetition around checking business permissions and calling check_business_tool_access, but every sentence otherwise earns its place.

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?

For a destructive write tool, it covers access gating and blocked-access handling well. However, the confirm requirement conflicts with the schema, and the description does not state what unpublishing does to the lead form's state or whether the action is reversible.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description introduces conflicting parameter guidance. It says "Requires confirm set to UNPUBLISH," while the schema does not list confirm as required and its description says to pass an exact literal "for example DELETE." This contradiction about the confirmation value and requirement reduces clarity.

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 description clearly states the specific verb and resource: "Unpublish a lead form." It is distinguishable from publish_lead_form and delete_lead_form by naming the exact action, though it does not explicitly contrast those siblings.

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 gives explicit preconditions and exclusions: check business permissions before offering or collecting inputs, FREE businesses cannot use it, call check_business_tool_access first, show grace-period warnings, and never proceed when access is blocked. This is strong when-to-use and when-not-to-use guidance.

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

All Nas.com toolsInspect
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