Trusoro

Edit a listing

update_listing

Idempotent

Fill in or edit the listing: name, description, services, service_area (other cities served), hours, social, phone, website, industry_label. A complete listing can appear in Google, is shown higher in its city and appears in the cities it serves. Needs an API key the confirmed owner approved.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "update_listing"
  }
}

Input Schema

Name	Required	Description
`name`	No	The business name as customers know it. A spelling fix is saved at once; a name with a phone, web address, promotion or an added city waits for a check by Trusoro.
`hours`	No	Opening hours in schema.org form, e.g. "Mo-Fr 08:00-17:00; Sa 09:00-13:00" (shown as a table and marked up for search); other text is shown as written.
`phone`	No	New public phone.
`social`	No	Links to the business pages on Google, Facebook, Instagram, Yelp, Nextdoor and similar sites. Other sites are refused.
`website`	No	New website.
`services`	No	Services offered, e.g. ["AC repair", "Duct cleaning"].
`listing_id`	Yes
`description`	No	New description.
`service_area`	No	Other cities served; the listing also shows on those city pages.
`industry_label`	No	What the business does.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-open-world mutation, so the description's added value is the auth prerequisite ("an API key the confirmed owner approved") and the downstream effects of completeness — Google visibility, higher city ranking, appearance on served-city pages. It omits that some edits (e.g. a name with a phone or promotion) enter a review queue, though the schema covers that per field.

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?

Three sentences: the editable surface first, the payoff second, the access requirement last. The field enumeration is dense but front-loaded and functional; little is wasted, though the list largely duplicates the schema keys.

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 10-parameter mutation with no output schema, the description covers what can be changed, what the result buys the business, and the authorization requirement. The main gap is that it never states explicitly that this is a partial update that leaves unspecified fields untouched, and moderation/review behavior is left entirely to the schema.

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 90%, so the schema already explains nearly every field, including the schema.org hours format and the social-link allowlist. The description only re-enumerates the fields and adds the gloss "service_area (other cities served)", which the schema also states.

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?

"Fill in or edit the listing" gives a specific verb and resource, and the following list of editable fields makes the scope unambiguous. It stops short of differentiating itself from submit_listing or prefill_from_website, so an agent must infer that this tool edits an existing record rather than creating one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool edits an existing listing (listing_id required) and requires an API key approved by the confirmed owner, which is a useful prerequisite. There is no explicit statement of when to use this instead of submit_listing for a new listing or get_listing to read current values.

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

All Trusoro 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?