Skip to main content
Glama
muend

arcgis-mcp-bridge

by muend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_text_element

Update the text content of a named layout element in an ArcGIS Pro project. Automate titles, dates, and labels before export.

Instructions

Update the text content of a named layout text element using arcpy.mp layout elements. Use this to automate titles, dates, subtitles, map numbers, project names, notes, or report labels before export. This modifies the selected layout and saves the .aprx project when save=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.3
    • changedInput schema / $defs / UpdateTextElementInput / properties / aprx_path / description
      Previous value: -"Absolute .aprx path."New value: +"Absolute path to the saved ArcGIS Pro .aprx project file. The path must be inside a configured PathGuard allowed root. Tools operate on the saved project file, not a live open ArcGIS Pro session."
  2. Changed5 schema fields changedv1.0.1
    • addedInput schema / $defs / UpdateTextElementInput / description
      Added value: +"Update the text content of a named layout text element."
    • changedInput schema / $defs / UpdateTextElementInput / properties / element_name / description
      Previous value: -"Text element name."New value: +"Name of the text element to update in the selected layout."
    • changedInput schema / $defs / UpdateTextElementInput / properties / layout_name / description
      Previous value: -"Layout name; None targets the first layout."New value: +"Name of the layout inside the .aprx project. Use None to target the first layout returned by ArcGIS Pro."
    • addedInput schema / $defs / UpdateTextElementInput / properties / new_text / description
      Added value: +"New text content to write into the layout element. Use an empty string to clear the element."
    • addedInput schema / $defs / UpdateTextElementInput / properties / save / description
      Added value: +"When true, save the .aprx project after updating the text element."
  3. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It mentions modification of the layout and optional save, but lacks details on error handling (e.g., missing element), licensing (arcpy.mp), or the effect when save=false (modification still occurs). This is adequate but not thorough.

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?

The description is extremely concise, using three sentences to convey purpose, use cases, and save behavior. Every sentence adds value with no redundancy.

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?

Given no annotations and 5 parameters, the description is too brief. It omits how layout selection works, behavior on missing elements, and prerequisites like project file state. The output schema exists but is not shown; still, the description should be more complete for safe usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has parameter descriptions, but context signals indicate 0% coverage (likely meaning no useful descriptions). The tool description adds context for use cases but does not explain parameter meanings beyond what the schema provides. For a tool with 5 parameters, this is insufficient.

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 description clearly states the verb 'Update' and the resource 'text content of a named layout text element', and lists specific use cases (titles, dates, etc.), making the purpose unmistakable. It is distinct from sibling tools, none of which update text elements.

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?

The description tells when to use ('automate titles, dates, subtitles... before export') and mentions the optional save behavior. However, it does not explicitly state when not to use or provide alternatives, though no direct sibling exists.

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

Deploy Server

Other Tools