Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

delete_component

Deletes a SketchUp group or component instance using its entity ID, so you can remove specific model objects by ID; raw faces and edges are not supported.

Instructions

Delete a group or component instance by entity ID. Raw faces, edges and other entities fail with -32602.

Returns: JSON {ok: true}.

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": {
      "id": "<id>"
    },
    "name": "delete_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntity ID from a previous response (integer or its string form)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • removedInput schema / properties / id / type
      Removed value: -"string"
  2. First observedv0.0.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the failure mode (error code -32602 for unsupported entity types) and the return shape, which is useful. But it omits key delete semantics: whether child entities are deleted with the parent, whether the operation is undoable, and whether it requires the instance to be unique versus a definition shared elsewhere.

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?

Two short sentences plus a return note, with the core operation and its validity constraint front-loaded. Nothing redundant; the error code carries real information.

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

Completeness3/5

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

An output schema exists, so explaining the return value is optional (the description does so anyway). For a destructive, no-annotation tool, the missing pieces are cascade behavior and undo availability, which an agent arguably needs before deleting a component instance.

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 is 100% and the schema already explains the id parameter as 'Entity ID from a previous response'. The description adds constraint meaning beyond that by limiting the valid ID to groups/component instances, which is the crucial semantic the schema lacks.

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 states a specific verb and resource ('Delete a group or component instance by entity ID') and explicitly bounds the accepted entity types, distinguishing it from sibling mutation tools like transform_component or create_component. An agent can identify the operation and target object type without opening the schema.

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

Usage Guidelines3/5

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

It states the negative case clearly ('Raw faces, edges and other entities fail with -32602'), which implies this tool is only for group/component instances. However, it never names an alternative for deleting raw geometry, so the agent is told what not to pass but not what to use instead.

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