FirmLedger

Edit one of my listings

update_my_listing

Change fields on a listing the user owns (name, tagline, description, website, email, phone, country, city, region, address, logo_url, founded, size, tags, socials) — the same service the dashboard edit form and PUT /api/v1/my/listings/:id use, including the re-moderation rule when the core record changes. Requires the user's confirmation.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No
`name`	No
`size`	No
`tags`	No
`email`	No
`phone`	No
`region`	No
`address`	No
`country`	No
`founded`	No
`listing`	Yes	The company: its FirmLedger slug (best — returned by search_listings), its exact name, its FirmLedger ID such as "FL-00012", or its FirmLedger profile URL.
`socials`	No	Social profile links keyed by network; use an empty object to clear. A JSON object string is also accepted.
`tagline`	No
`website`	No
`logo_url`	No
`description`	No
`confirmation_token`	No	Leave empty on the first call: you get an action_summary and a token instead of the action. After the user explicitly confirms that summary, call again with the SAME arguments plus this token.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

addedInput schema / properties / socials / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "facebook": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "instagram": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "linkedin": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "x": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "youtube": {
+        "maxLength": 500,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "maxLength": 800,
+    "type": "string"
+  }
+]

addedInput schema / properties / socials / description

Added value: +"Social profile links keyed by network; use an empty object to clear. A JSON object string is also accepted."

removedInput schema / properties / socials / maxLength
```
Removed value: -800
```
removedInput schema / properties / socials / type
```
Removed value: -"string"
```

AddedSep 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive. The description adds two traits the annotations cannot convey: edits can trigger a re-moderation rule when the core record changes, and the mutation is gated behind explicit user confirmation. It does not say how to clear a field or what the confirmation summary contains, keeping it below a 5.

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 change operation and its scope are front-loaded in the first clause, with the confirmation requirement as a short second sentence. The parenthetical field list is dense but functional; nothing reads as filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter mutation with no output schema, it covers the confirmation gate, re-moderation consequence, and editable surface. It leaves partial-update semantics (what happens to omitted fields) and failure modes unspecified, which is the main remaining gap.

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 only 18%, so the description must carry more weight. It lists the editable field names, which confirms the editable set but largely restates schema property keys with no format, requiredness, or clearing semantics beyond what the schema already documents for listing, socials, and confirmation_token.

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 (change fields) and resource (a listing the user owns), then enumerates the editable fields and equates the tool with the dashboard edit form and PUT /api/v1/my/listings/:id. This clearly separates it from read siblings like get_my_listings and from the prepare_* siblings.

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?

Gives the precondition that the user must own the listing and explicitly says confirmation is required, with the token flow described in the schema. It stops short of naming alternatives (e.g., prepare_listing_submission vs. this tool) or stating when-not to use it, so it is clear context rather than full routing guidance.

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

All FirmLedger tools Inspect

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

Need Help?