Skip to main content
Glama

install_userscript

Install a userscript or user style from a URL or pasted text and save it unchanged, supporting sources such as Greasy Fork and OpenUserJS.

Instructions

Install a userscript (.user.js) or user style (.user.css) from a URL, such as Greasy Fork, OpenUserJS or userstyles.world, or from pasted text. It is saved unchanged. @require'd libraries and style preprocessors (Stylus, Less) are not supported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "install_userscript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose key traits: the content is persisted unchanged rather than just applied, and @require'd dependencies and CSS preprocessors are rejected. Not covered: overwrite/duplicate-install behavior, whether installation takes effect immediately, and failure handling for unreachable URLs.

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 tight sentences, front-loaded with the verb and resource, followed by the constraint. Every clause carries information: sources, persistence, and the two exclusion cases.

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?

For a two-parameter mutation tool with no annotations and no output schema, the definition covers source types and limitations but omits the one-of url/text requirement, duplicate/replace semantics, and any indication of what a successful install returns. Adequate to start, but the agent still has gaps before calling correctly.

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

Parameters3/5

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

Schema coverage is 0%, and the description does map the two params reasonably — 'url' as a source link from script hosting sites, 'text' as pasted source. However, with 0 required parameters it never states that url and text are alternatives and that one must be supplied, leaving the agent to guess the interaction between them.

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?

Specific verb (install) plus two concrete resources (.user.js userscript / .user.css user style) and the two accepted sources (URL or pasted text). The phrase 'saved unchanged' distinguishes it from transient siblings like apply_css or run_js without needing to name them.

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 gives positive context for use (URL from Greasy Fork/OpenUserJS/userstyles.world, or pasted text) and states what is unsupported (@require, Stylus/Less). It never says when to choose this over apply_css or run_script, nor how to handle an already-installed script, so guidance is implied rather than explicit.

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