Fotor

Get Website Url

get_website_url

Get a one-time signed-in link to the configured Fotor website.

Request a new link if it expires or was already used.

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_website_url"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`expires_in`	Yes	Link lifetime in seconds.
`handoff_url`	Yes	One-use sign-in URL. Present as a clickable link in the user's language; never fetch, preview or preflight it, as the first visit consumes it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

addedOutput schema / properties / expires_in / description
```
Added value: +"Link lifetime in seconds."
```

addedOutput schema / properties / handoff_url / description

Added value: +"One-use sign-in URL. Present as a clickable link in the user's language; never fetch, preview or preflight it, as the first visit consumes it."

First observedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds context beyond the annotations by disclosing that the link is single-use and expiring, which is consistent with idempotentHint=false and readOnlyHint=false (a token is minted and consumed). It stops short of stating the link's lifetime or any auth requirements for the caller.

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, zero waste, with the one-time nature front-loaded and the refresh rule following immediately.

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?

With no parameters, an output schema present, and annotations covering the safety profile, the description supplies everything an agent needs: what the call yields and how to recover from an expired or consumed link.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-param schema applies.

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?

States a specific verb and resource ('get a one-time signed-in link to the configured Fotor website') with a meaningful qualifier that distinguishes it from get_upload_url or get_credits. It does not explicitly name a sibling, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives a concrete re-invocation rule: request a new link if it expires or was already consumed. That is real usage guidance for a one-time credential, though it never says when the initial call is warranted or contrasts it with other get_* tools.

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

All Fotor 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?