Skip to main content
Glama

login

Authenticates with Strapi CMS using admin email and password, then stores a session token for subsequent requests. Call it before other tools to enable authenticated content management.

Instructions

Authenticate with Strapi CMS. Call this FIRST before any other tool. Requires the user's admin email and password. On success, stores a session token for subsequent requests. If the user hasn't provided credentials, ask them for their Strapi admin email and password.

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": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesStrapi admin email
passwordYesStrapi admin password

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses a side effect (storing a session token for subsequent requests) and the prerequisite ordering. It stops short of covering failure behavior or token lifetime, which an agent might want.

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?

Four short sentences, front-loaded with the action and the ordering rule. The credential requirement is stated twice ('Requires the user's admin email and password' then the ask-the-user instruction), a small redundancy that still serves agent 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?

For a two-parameter authentication tool with no output schema, the description covers purpose, ordering, side effect, and missing-input handling. Only error/expiry semantics are absent, which is minor for this complexity.

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 100% and both fields are already documented, so the description only adds that these are the user's Strapi admin credentials. That is mildly useful framing but no new syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Authenticate with Strapi CMS') and immediately clarifies its role as the mandatory first step, which distinguishes it from siblings like get_session or any entry-level tool.

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

Usage Guidelines5/5

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

Explicitly says to call it FIRST before any other tool and gives concrete handling for the missing-credentials case ('ask them for their Strapi admin email and password'), leaving no inference about when to invoke it.

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