jizura_clickFind and click buttons by visible text in JIZURA's kinetic typography editor, using partial or exact matching to automate style, export, and theme actions.
表示テキストでボタンを探してクリックする。例: 'おまかせで作る'、'シャッフル'、'次の案'、'MP4 を書き出す'、'テーマ設定'、'適用'。
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ボタンの表示テキスト（部分一致） | |
| exact | No | trueで完全一致のみ |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states the click action, omitting side effects, post-click behavior, error handling, or whether it waits for the element.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence with illustrative examples; no filler. Efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple click tool with no output schema, the description covers purpose and parameter examples. However, with no annotations, it lacks behavioral details an agent might need to invoke correctly, such as what happens after clicking.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully documents both parameters, but the description adds concrete examples of button text values for the 'name' parameter, which helps an agent pick appropriate values. It does not explain the 'exact' parameter, which remains schema-only.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (click) and resource (a button found by display text), with concrete examples of button labels. It clearly distinguishes from sibling tools that set checkboxes or fill fields, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this tool versus siblings like jizura_set_checkbox or jizura_fill, nor any prerequisites or exclusions. The examples illustrate parameter values, not usage contexts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.