OpenClip

Get Account Tool

get_account

Read-only

Return the connected OpenClip account: the user's id and email, the current team and plan, the number of processing credits remaining, and the granted scopes/abilities of the current connection (the OAuth scopes for the primary connection, or the personal access token abilities for a key-based connection). Use this first to confirm the connection works and the user has credits before submitting videos.

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": "get_account"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	Coarse billing state of the current team.
`team`	Yes	The current team's name. Null when the account has no team yet.
`email`	Yes	The connected user's email address.
`user_id`	Yes	The connected user's id (hashid).
`abilities`	Yes	Granted OAuth scopes (primary connection) or personal access token abilities (key-based connection).
`credits_remaining`	Yes	Processing credits left. One credit = one minute of source video.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "abilities": {
+      "description": "Granted OAuth scopes (primary connection) or personal access token abilities (key-based connection).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "credits_remaining": {
+      "description": "Processing credits left. One credit = one minute of source video.",
+      "type": "integer"
+    },
+    "email": {
+      "description": "The connected user's email address.",
+      "type": "string"
+    },
+    "plan": {
+      "description": "Coarse billing state of the current team.",
+      "enum": [
+        "free",
+        "trial",
+        "paid"
+      ],
+      "type": "string"
+    },
+    "team": {
+      "description": "The current team's name. Null when the account has no team yet.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "user_id": {
+      "description": "The connected user's id (hashid).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "user_id",
+    "email",
+    "team",
+    "plan",
+    "credits_remaining",
+    "abilities"
+  ],
+  "type": "object"
+}

First observedJul 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations are provided, but the description carries the burden well: it identifies the operation as returning account/connection details and explains that it verifies credentials and credit availability. It doesn't mention error/expired-token behavior or whether it consumes credits, but the core behavioral contract is clear.

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?

One dense, front-loaded sentence listing return fields, followed by an actionable usage directive. No filler or repetition.

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

Completeness5/5

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

For a zero-parameter read-only endpoint, it fully describes what the agent gets (identity, plan, credits, scopes) and why to call it first. No output schema is present, but the description enumerates all meaningful return contents, so an agent can act on the result.

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?

There are zero parameters, so schema cannot add meaning. Baseline 4 applies; the description properly focuses on the return payload instead of inventing parameter detail.

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 ('Return') and enumerates the exact contents: user id/email, team/plan, credits remaining, and granted scopes. This is clearly distinguished from render/status/job tools in the sibling list, so an agent knows exactly what this tool is for.

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 'Use this first to confirm the connection works and the user has credits before submitting videos.' This gives the agent a concrete trigger condition and sequencing relative to submission tools.

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

All OpenClip tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?