Skip to main content
Glama

AccountHub

by ai.accounthub
OverviewDiscussionsAdmin

update_shared_item

Destructive

Edit the title, body or due date of an item you placed in an AccountHub shared project (shared project) — NOT a Slack workspace — or, with mark_decided: true, turn an open question into a decision. Only the person who placed an item can edit its text, and only while still a member; mark_decided follows who may close the question (its placer, anyone while unassigned, or its assignee). To change who does it use reassign_shared_item, to change its state use complete_shared_item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoNew body; null clears it.
titleNoNew title.
item_idYesThe item id (from list_shared_items).
due_dateNoNew deadline YYYY-MM-DD; null clears it.
mark_decidedNotrue = turn an open question into a decision (who decided it and when is recorded). Send it alone, without title/body/due_date. Allowed for whoever may close the question: its placer, anyone while it is unassigned, or its assignee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mark_decided
      Added value: +{
+  "description": "true = turn an open question into a decision (who decided it and when is recorded). Send it alone, without title/body/due_date. Allowed for whoever may close the question: its placer, anyone while it is unassigned, or its assignee.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses the full authorization model: only the placer may edit text, membership is required, and mark_decided is gated on placer / unassigned-anyone / assignee. It does not say whether edits are reversible or what happens on a permission failure, which would round out a mutation tool flagged destructive.

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 core action and the Slack-workspace exclusion are front-loaded in the first clause, and the alternatives close the paragraph. It is dense and slightly long due to the parenthetical permission rules, but every sentence carries routing information.

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 mutation tool with no output schema, the description covers both operating modes, the permission gates, and the sibling boundaries an agent needs. The only gap is failure/response behavior when the caller is unauthorized.

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 description coverage is 100% and already documents each field, including 'null clears it' and the mark_decided rules, so the baseline is 3. The description adds only the cross-cutting constraint that mark_decided must be sent alone, which is largely restated from the schema.

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 and resource (edit title/body/due date of an item in an AccountHub shared project) and immediately disambiguates the namespace by excluding a Slack workspace. It also names two sibling tools (reassign_shared_item, complete_shared_item) so the agent can route without opening schemas.

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 when-to-use ('only the person who placed an item can edit its text, and only while still a member'), the alternate mode (mark_decided turns an open question into a decision), and explicit alternatives for adjacent operations (reassign for ownership, complete for state). Nothing is left to inference.

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

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