Skip to main content
Glama

goals_update

Update goal properties such as title, type, assignee, target value, or duration. Changes take effect immediately in goal tracking.

Instructions

Update an existing goal.

Updates goal properties such as title, type, assignee, expected outcome, duration, or interval.

Workflow tips:

  • Use goals/list to find the goal ID first

  • Only include fields you want to update

  • Changes take effect immediately in goal tracking

Common use cases:

  • Adjust target value: { "id": "goal-id", "expected_outcome": { "target": 50000, "tracking_metric": "sum" } }

  • Change assignee: { "id": "goal-id", "assignee": { "id": 456, "type": "person" } }

  • Update title: { "id": "goal-id", "title": "New Goal Title" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the goal to update
titleNoGoal title
typeNoGoal type configuration
assigneeNoUser or team assigned to this goal
expected_outcomeNoExpected outcome configuration
durationNoGoal duration period
intervalNoGoal interval
Behavior3/5

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

No annotations provided. Description mentions 'changes take effect immediately' and implies mutation. Does not disclose return format or validation behavior, but adds some behavioral context beyond no annotations.

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

Conciseness5/5

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

Concise but informative: general statement, updatable fields list, workflow tips, common use cases with JSON. Front-loaded and every sentence earns its place.

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?

Given complexity (7 params, nested objects, no output schema), description provides enough context with examples and workflow tips. Does not explain return values, but acceptable given no output schema.

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 100%, so baseline 3. Description adds value with examples showing structure for nested objects like expected_outcome and assignee, and clarifies usage patterns.

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?

Clear verb 'Update' with resource 'existing goal', lists updatable fields, and provides examples. Differentiates from siblings like goals_create, goals_delete, goals_list.

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?

Provides workflow tips (get goal ID via goals/list, update only desired fields, immediate effect) but lacks explicit when-not-to-use or alternatives. Good context for typical use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamsamuelfraga/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server