Skip to main content
Glama
Chrome Profile Manager

Chrome Profile Manager

by megamen32

profile_extension_get

Reads an extension from a paired Chrome profile by profile ID and extension ID, enabling inspection of its details.

Instructions

Read an extension in a paired existing profile

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": {
      "profile_id": "<profile_id>",
      "extension_id": "<extension_id>"
    },
    "name": "profile_extension_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYes
extension_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. 'Read' implies a non-mutating operation, but nothing is said about error behavior for an unpaired profile or missing extension, permissions required, or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the verb and scope front-loaded and no filler. It is efficient, though its brevity is partly under-specification rather than disciplined concision.

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?

This is a simple two-parameter read tool with no output schema and no annotations, so the description is the only place to explain the return value and failure modes. It explains neither, leaving the agent unable to predict the response shape or error conditions.

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?

Schema description coverage is 0% for two required string parameters, so the description must compensate and does not. It never mentions profile_id or extension_id, leaving their format and relationship (e.g. which profile pairing is required) unexplained beyond the parameter names themselves.

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 names a specific verb (Read) and resource (an extension in a profile), which is enough to tell it apart from list-oriented siblings like profile_extensions_list. The only weakness is the ambiguous phrase 'paired existing profile', which is not defined here.

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 statement of when to use this versus profile_extensions_list or the profile_helper_* tools, and no explicit prerequisites. The phrase 'paired existing profile' hints at a precondition (the profile must already be paired) but does not say what to do if it is not.

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