Skip to main content
Glama
Sign In

Boomerang

by ai.getboomerang
OverviewDiscussionsAdmin

Update company profile

update_company_profile
DestructiveIdempotent

Save changes to the workspace's company profile in Boomerang. The change is persistent and shared: the saved profile is what everyone in the workspace sees when they open the company profile, and it replaces the previous values of the sections you send (there is no undo). Merges only the sections you provide — pass just the fields being changed in data, and optionally an explicit sections list. When sections is empty, only populated data fields are merged. Pass sections=["ALL"] to replace the entire document.

Use when: Use when the user asks to change their company profile or saves edits from the get_company_profile artifact UI. Pass only changed sections in data (e.g. value_proposition and pain_points), not the full document. Confirm success in plain language, naming the sections that were updated; optionally re-render the UI with saved values.

Behavior: idempotent, destructive

workspace_id / user_id are injected from request headers.

Next steps (after this tool succeeds): [optional] [SUGGESTION] → call get_company_profile: Confirm save to the user in plain language. Optionally re-render the company profile artifact with the returned data.

Also returns pagination info (researched_on, company_name, company_url, one_line_summary, value_proposition, pain_points, proof_points, competitors, customer_industry_category, departments, seniority, title_keywords, company_size, named_customers, named_investors, title_regex, buying_committee, buying_committee_regex, customer_industry, extended_buying_committee, extended_buying_committee_regex).

Input Schema

NameRequiredDescriptionDefault
dataNo
sectionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / _triggered_by
      Removed value: -{
-  "default": "",
-  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
-  "type": "string"
-}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already flag idempotent/destructive, but the description adds substantive context they cannot carry: the change is persistent and workspace-shared, it replaces prior values for the sections sent, there is no undo, and merging is section-scoped with a special sections=["ALL"] full-replace mode. It also discloses that workspace_id/user_id are injected from headers, which affects nothing the caller must supply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core guidance is well front-loaded and sectionalized, but the final sentence ("Also returns pagination info (researched_on, company_name, ...)") is a long, mislabeled enumeration — those are profile field names, not pagination — and adds noise rather than information. That trailing block dilutes an otherwise tight description.

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 destructive, nested-object merge tool with 0% schema description coverage, the description covers persistence, merge scope, the full-replace escape hatch, header-injected IDs, and the follow-up call. An output schema exists so return values need not be explained, yet the trailing return-field list is confusing and slightly undermines an otherwise complete picture.

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 description coverage is 0% and `data` is a free-form object, so the description must carry the burden — and it does, defining merge semantics, the empty-sections behavior (only populated data fields merged), and the ["ALL"] sentinel for `sections`. It stops short of specifying the field names/shape accepted inside `data` beyond examples (value_proposition, pain_points).

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?

The first sentence states a specific verb and resource ("Save changes to the workspace's company profile in Boomerang") and the surrounding text makes clear this is the write counterpart to the read-side get_company_profile sibling. An agent can distinguish it from other update_* siblings 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?

There is an explicit "Use when" block naming both trigger conditions (user asks to change the profile, or saves edits from the get_company_profile UI), plus concrete guidance on what to pass (only changed sections, not the whole document) and an explicit next step routing to get_company_profile. Alternatives and conditions are spelled out rather than implied.

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

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