Skip to main content
Glama

Agent Company Index

by com.agentcompanyindex
OverviewDiscussionsAdmin

Approve listing draft

approve_listing
DestructiveIdempotent

Approve publication of the exact draft revision on behalf of the company and accept the Listing Terms (LT-2, https://agentcompanyindex.com/legal/listing-terms/lt-2) for it. Requires a verified domain. Before calling: show the user the draft, then the listing_terms summary and link from get_listing_status, and ask whether they may act for the company, approve this exact revision and accept the Listing Terms on the company's behalf. Call only after an explicit yes from that person; never on your own. Pass the approver's full name, role and the company's legal name. When the domain was confirmed with a DNS record or a file, also pass approver_email (an address on the company domain the approver reads): ACI mails it a confirmation link and publication waits for it. The approved revision is then published automatically, usually within minutes; the approver gets an email record of the approval and the terms. When the domain was confirmed with the emailed code, ACI sends a free monthly report (which AI assistants and systems retrieved the profile) to that address; set monthly_report to false if the user does not want it. Every report has an unsubscribe link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
revisionYes
referenceYes
approver_nameYesFull name of the person approving for the company.
approver_roleYes
listing_tokenYes
approver_emailNoRequired when the domain was confirmed with a DNS record or a file: an address on the company domain the approver reads. Ignored when the domain was confirmed with the emailed code (that address is recorded).
monthly_reportNoSend the monthly report to the confirmed work address (default true).
schema_versionYes
user_confirmationNoOptional: the user's reply agreeing to approve and to the Listing Terms, quoted word for word.
company_legal_nameYesThe company's legal name (e.g. from its imprint), the party accepting the Listing Terms.
accept_listing_termsYesSet to "LT-2" only after the user explicitly accepted the Listing Terms (https://agentcompanyindex.com/legal/listing-terms/lt-2) on behalf of the company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / accept_listing_terms / const
      Previous value: -"LT-1"New value: +"LT-2"
    • changedInput schema / properties / accept_listing_terms / description
      Previous value: -"Set to \"LT-1\" only after the user explicitly accepted the Listing Terms (https://agentcompanyindex.com/legal/listing-terms/lt-1) on behalf of the company."New value: +"Set to \"LT-2\" only after the user explicitly accepted the Listing Terms (https://agentcompanyindex.com/legal/listing-terms/lt-2) on behalf of the company."
  2. Changed7 schema fields changed
    • addedInput schema / properties / accept_listing_terms
      Added value: +{
+  "const": "LT-1",
+  "description": "Set to \"LT-1\" only after the user explicitly accepted the Listing Terms (https://agentcompanyindex.com/legal/listing-terms/lt-1) on behalf of the company."
+}
    • addedInput schema / properties / approver_email
      Added value: +{
+  "description": "Required when the domain was confirmed with a DNS record or a file: an address on the company domain the approver reads. Ignored when the domain was confirmed with the emailed code (that address is recorded).",
+  "maxLength": 320,
+  "type": "string"
+}
    • addedInput schema / properties / approver_name
      Added value: +{
+  "description": "Full name of the person approving for the company.",
+  "maxLength": 200,
+  "minLength": 2,
+  "type": "string"
+}
    • addedInput schema / properties / company_legal_name
      Added value: +{
+  "description": "The company's legal name (e.g. from its imprint), the party accepting the Listing Terms.",
+  "maxLength": 200,
+  "minLength": 2,
+  "type": "string"
+}
    • addedInput schema / properties / monthly_report
      Added value: +{
+  "default": true,
+  "description": "Send the monthly report to the confirmed work address (default true).",
+  "type": "boolean"
+}
    • addedInput schema / properties / user_confirmation
      Added value: +{
+  "description": "Optional: the user's reply agreeing to approve and to the Listing Terms, quoted word for word.",
+  "maxLength": 500,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "schema_version",
-  "reference",
-  "listing_token",
-  "revision",
-  "approver_role"
-]New value: +[
+  "schema_version",
+  "reference",
+  "listing_token",
+  "revision",
+  "approver_role",
+  "approver_name",
+  "company_legal_name",
+  "accept_listing_terms"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint, openWorldHint) it discloses the domain-verification prerequisite, the conditional approver_email requirement when verification used DNS/file, that publication waits on the emailed confirmation link, that publication follows automatically within minutes, and that approval/report emails are sent. This is materially more than the structured fields provide.

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?

Long, but front-loaded with the core action and legal acceptance before the procedural guidance, and nearly every sentence carries a distinct constraint (verified domain, explicit consent, email confirmation, report opt-out). The paragraph form is dense; a short break between consent flow and post-call behavior would aid scanning.

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 an 11-parameter, destructive, open-world tool with no output schema, the description covers preconditions, consent requirements, conditional parameters, and post-call outcomes (automatic publication, confirmation email, monthly report). An agent has everything needed to invoke it correctly.

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 coverage is only 55%, and the description compensates: it explains the approver_email condition (required for DNS/file verification, ignored for emailed-code verification), the monthly_report toggle and its unsubscribe link, and which identity fields to supply (full name, role, legal name). It says nothing about revision, reference, listing_token or schema_version, but those are largely self-evident or schema-constrained.

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 precise verb and object — approve publication of the exact draft revision and accept Listing Terms LT-2 — with the scope ('the exact draft revision') that separates it from get_listing_status, request_listing and update_listing_answers. An agent can identify the action without opening the 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 and sequencing: requires a verified domain, show the user the draft and the listing_terms summary/link, confirm authority to act for the company, and call only after an explicit yes — 'never on your own.' It also names which fields to pass, leaving nothing to inference.

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

All Agent Company Index toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources