Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

Update share link

formShareLink_update

Also the "delete" path — pass revoked:true to permanently disable a link (no separate _delete tool).

Update a share link's settings (provide at least one field).

  • expiresAt: future ms timestamp; 0 clears.

  • maxClaims: positive integer; -1 clears.

  • customDomainId + customSlug: attach a verified custom domain (look up via formShareLink_list); both required together. Slug = 3-64 chars, lowercase alphanumeric + hyphens. Pass both null to detach.

  • revoked: true → permanently stop the link from accepting new submissions (irreversible, cannot combine with other fields). Use for any "remove this link" intent — works for both never-shared cleanup and audit-trail-preserving revocation.

Input Schema

NameRequiredDescriptionDefault
revokedNo
expiresAtNo
maxClaimsNo
customSlugNo
shareLinkIdYes
customDomainIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / customSlug / anyOf
      Removed value: -[
-  {
-    "maxLength": 64,
-    "minLength": 3,
-    "pattern": "^[a-z0-9][a-z0-9-]*[a-z0-9]$|^[a-z0-9]{3,}$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / customSlug / maxLength
      Added value: +64
    • addedInput schema / properties / customSlug / minLength
      Added value: +3
    • addedInput schema / properties / customSlug / pattern
      Added value: +"^[a-z0-9][a-z0-9-]*[a-z0-9]$|^[a-z0-9]{3,}$"
    • addedInput schema / properties / customSlug / type
      Added value: +[
+  "string",
+  "null"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior2/5

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

The description is unusually rich about behavior — irreversibility of revocation, clear-versus-set semantics for expiresAt (0) and maxClaims (-1), and pair-wise parameter coupling. However, it explicitly frames this tool as the "delete" path that "permanently" and "irreversibly" disables a link, which conflicts with the destructiveHint=false annotation; an agent trusting the annotation could treat this as a safe, non-destructive update. The description corrects the annotation rather than repeating it, but the inconsistency still misrepresents the operation's safety profile.

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?

Front-loads the unconventional delete-path behavior before the routine parameter list, and the bullet structure maps cleanly to the schema fields. Slightly verbose on the revoked bullet (the "never-shared cleanup" rationale is repeated twice), but nothing is wasted enough to obscure the call.

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?

For a mutation tool with no output schema and 6 parameters at 0% schema coverage, the description covers every field's accepted values, clearing conventions, coupling constraints, and irreversibility. An agent has everything needed to invoke it correctly without further documentation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so: expiresAt semantics ("future ms timestamp; 0 clears"), maxClaims ("positive integer; -1 clears"), customDomainId+customSlug coupling, slug format/length rules, and the null-to-detach convention. This is meaningfully more than the bare schema types and patterns.

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?

States a specific verb+resource ("Update a share link's settings") and immediately discloses the dual role as the delete path, explicitly noting there is no separate _delete tool. An agent can distinguish it from formShareLink_create/list/create without opening any schema.

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?

Gives explicit preconditions ("provide at least one field"), routes domain lookups to formShareLink_list, and prescribes the exact field to use for removal intent ("revoked:true ... Use for any 'remove this link' intent"). It also states a mutual-exclusion rule (revoked cannot combine with other fields) and that customDomainId+customSlug must be supplied together.

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

All Formstep 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