Skip to main content
Glama

update_proposal

Update an existing proposal to track execution progress.

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": {
      "workspaceId": "<workspaceId>",
      "editId": "<editId>"
    },
    "name": "update_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
editIdYesThe edit ID
proposalIdNoSpecific proposal ID to update
sourceMediaNoAttach the original approved references without creating another proposal.
workspaceIdYesThe workspace ID
shotBindingsNoMap approved production job IDs to saved shot IDs; attach those exact starting images.
productionPlanNoExact production jobs, starting-image media IDs, settings and per-job cost limits. Required for combined plan/image/budget approval.
proposalSummaryNoUpdated short summary including models, cost and approval scope. Keep full details in proposalMarkdown.
proposalMarkdownNoUpdated proposal content with execution steps marked complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / productionPlan
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Exact production jobs, starting-image media IDs, settings and per-job cost limits. Required for combined plan/image/budget approval.",
      +  "properties": {
      +    "budgetUsd": {
      +      "maximum": 10000,
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "creativeScope": {
      +      "maxLength": 4000,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "jobs": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "aspectRatio": {
      +            "type": "string"
      +          },
      +          "duration": {
      +            "exclusiveMinimum": 0,
      +            "maximum": 600,
      +            "type": "number"
      +          },
      +          "jobId": {
      +            "pattern": "^[A-Za-z0-9_-]{1,200}$",
      +            "type": "string"
      +          },
      +          "kind": {
      +            "enum": [
      +              "video",
      +              "audio"
      +            ],
      +            "type": "string"
      +          },
      +          "maxCostUsd": {
      +            "maximum": 10000,
      +            "minimum": 0,
      +            "type": "number"
      +          },
      +          "model": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "modelSettings": {
      +            "additionalProperties": {
      +              "type": [
      +                "string",
      +                "number",
      +                "boolean"
      +              ]
      +            },
      +            "type": "object"
      +          },
      +          "prompt": {
      +            "maxLength": 12000,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "resolution": {
      +            "type": "string"
      +          },
      +          "sourceMediaId": {
      +            "$ref": "#/properties/productionPlan/properties/jobs/items/properties/jobId"
      +          },
      +          "stylePrompt": {
      +            "type": "string"
      +          },
      +          "voiceId": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "jobId",
      +          "kind",
      +          "model",
      +          "prompt",
      +          "duration",
      +          "maxCostUsd"
      +        ],
      +        "type": "object"
      +      },
      +      "maxItems": 40,
      +      "minItems": 1,
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "creativeScope",
      +    "budgetUsd",
      +    "jobs"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / shotBindings
      Added value: +{
      +  "description": "Map approved production job IDs to saved shot IDs; attach those exact starting images.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "jobId": {
      +        "$ref": "#/properties/productionPlan/properties/jobs/items/properties/jobId"
      +      },
      +      "shotId": {
      +        "$ref": "#/properties/productionPlan/properties/jobs/items/properties/jobId"
      +      }
      +    },
      +    "required": [
      +      "jobId",
      +      "shotId"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 40,
      +  "type": "array"
      +}
    • addedInput schema / properties / sourceMedia
      Added value: +{
      +  "description": "Attach the original approved references without creating another proposal.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "downloadUrl": {
      +        "description": "Firebase Storage download URL for the uploaded file",
      +        "type": "string"
      +      },
      +      "duration": {
      +        "description": "Audio/video duration if known",
      +        "type": "number"
      +      },
      +      "fileName": {
      +        "description": "Original uploaded file name",
      +        "type": "string"
      +      },
      +      "height": {
      +        "description": "Image/video height in pixels",
      +        "type": "number"
      +      },
      +      "intendedUse": {
      +        "description": "How the user intended this media to be used",
      +        "type": "string"
      +      },
      +      "mimeType": {
      +        "description": "MIME type of the uploaded file",
      +        "type": "string"
      +      },
      +      "size": {
      +        "description": "File size in bytes",
      +        "type": "number"
      +      },
      +      "slotId": {
      +        "description": "Optional attachment slot/context",
      +        "type": "string"
      +      },
      +      "storagePath": {
      +        "description": "Firebase Storage path of the uploaded file",
      +        "type": "string"
      +      },
      +      "width": {
      +        "description": "Image/video width in pixels",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "downloadUrl"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "workspaceId",
      -  "editId",
      -  "proposalMarkdown"
      -]New value: +[
      +  "workspaceId",
      +  "editId"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / proposalSummary
      Added value: +{
      +  "description": "Updated short summary including models, cost and approval scope. Keep full details in proposalMarkdown.",
      +  "maxLength": 1800,
      +  "minLength": 1,
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It never says whether productionPlan replaces or merges with an existing plan, whether attaching sourceMedia creates new records, whether the update is destructive to prior proposalMarkdown, or what permissions are required — significant omissions for a nested mutation tool.

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 single sentence is front-loaded and free of padding, so nothing is wasted. However, for a tool with 8 parameters and three nested object structures, nine words is undersized rather than well-proportioned.

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

Completeness2/5

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

The tool is complex — nested productionPlan with per-job cost limits, media attachments, shot bindings — and has neither annotations nor an output schema to shoulder the explanation. The description says nothing about transactionality, side effects, or what a successful update returns, so an agent cannot call it confidently beyond the schema itself.

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 each nested field (sourceMedia, shotBindings, productionPlan, proposalMarkdown) is already documented in the schema. The description adds only the framing that this is about tracking execution progress, which loosely hints that proposalMarkdown should mark steps complete but adds no syntax or constraint detail beyond the schema.

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?

The description states a specific verb and resource ('Update an existing proposal') plus an intent ('track execution progress'), which is clearer than a bare restatement of the name. It does not differentiate this tool from plausible siblings like save_proposal or set_proposal_status, leaving the agent to infer which mutation to choose.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., an existing proposal or edit context), and no indication of when to prefer save_proposal or set_proposal_status instead. The single clause about tracking progress implies a scenario but never routes the agent explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.