Skip to main content
Glama

Add text

snipaya_add_text

Add a text label at a chosen canvas or image pixel position, supporting multi-line text and optional styling to caption or annotate screenshots.

Instructions

Add a text label with its top-left corner at "at". Supports \n for new lines.

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": {
      "text": "<text>",
      "at": "<at>"
    },
    "name": "snipaya_add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesA point. Canvas coordinates, or image pixels when relativeTo is set.
textYes
styleNoOptional style. Omitted fields use the user’s current tool style. Brand colors: coral #EC534E, papaya #FE9440.
tabIdNoTarget tab id. Defaults to the active tab.
relativeToNoImage id from snipaya_get_canvas. When set, all coordinates in this call are pixels of that image as captured (the same pixels you see in snipaya_render of that image).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose that this is a non-destructive write operation. The description adds useful behavioral detail by specifying the top-left anchor point and newline support, but it does not describe side effects, defaults, or return behavior.

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 two short, front-loaded sentences with no wasted language. The positioning constraint is stated immediately, followed by the newline behavior.

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?

With annotations covering safety and the schema documenting most parameters, the description is complete enough to invoke the tool correctly. The main missing piece is sibling differentiation for selection among the many `add_*` tools.

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 80%, so the schema already documents most parameters. The description still adds meaningful semantics by clarifying that `at` is the label's top-left corner and that `text` supports `\n` newlines.

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: 'Add a text label.' It also specifies that the label's top-left corner is positioned at the `at` point. It does not explicitly differentiate this tool from sibling annotation tools such as `snipaya_add_callout`, so it falls short of a 5.

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?

The description does not say when to use this tool versus alternatives like `snipaya_add_callout` or `snipaya_add_shape`. It only states what the tool does, leaving selection guidance entirely implicit.

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