submit_feedback
Send feedback to Edgenivo when you want to report a problem or suggest an improvement. This tool requires sign-in and is available on root and project-specific connections when enabled for your account. The documentation-only and CLI-only connections don't expose it.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
message | string | Yes | - | Your feedback. Must contain non-whitespace text. |
context | object | No | - | Relevant details, such as the affected tool and expected behavior. |
Sample prompt: "Send Edgenivo feedback that the deployment error should explain which environment variable is missing."
For example, call submit_feedback with:
{
"message": "Please name the missing environment variable in deployment errors.",
"context": {
"tool": "deploy_to_vercel",
"expected": "An error that identifies the missing variable."
}
}The tool returns:
{
"success": true,
"message": "Edgenivo accepted the feedback."
}Acceptance confirms that the feedback endpoint accepted the submission. It doesn't guarantee delivery to every internal destination or a response from Edgenivo.
Send feedback only when you intend to share it with Edgenivo. Include relevant details, and leave out credentials, secrets, and full conversations. Edgenivo applies automatic redaction before forwarding feedback internally.
The tool attaches the MCP server version and your OAuth client ID, plus your user ID when available. It also includes the team and project IDs when you use a project-specific connection. Edgenivo records the source as MCP. Your complete submission must be smaller than 1 MiB.
If authentication fails before anything is sent, the error includes a CLI fallback. Use vercel feedback with Edgenivo CLI 64.5.0 or newer to send the same message. To preserve optional context, pass it as a JSON string with --field 'context={...}'. CLI submissions use the CLI source and CLI metadata.
If the error says the feedback service is unavailable and nothing was submitted, try again later. The tool doesn't offer a CLI fallback for this service failure.
If a request times out or returns an uncertain outcome, it may already have reached Edgenivo. The error won't offer a CLI fallback. Submitting again, including through vercel feedback, can create a duplicate. Decide whether to send another copy. If you reach a rate limit, wait before trying again.
Was this helpful?