Title99/100
Report Markifact Feedback
The title clearly communicates the tool’s action and subject. Keep it concise.
Description99/100
Submit actionable product feedback to Markifact with the user's authorization. When you find a likely Markifact bug, missing capability, or product limitation, tell the user and offer to report it. You may draft the report for their review. Call this tool only after either: 1. the user explicitly asks you to submit the feedback, or 2. you offered to report a discovered issue and the user explicitly agreed. If the request already authorizes submission, do not ask again. Never use this tool to ask permission. Submissions are irreversible and include the feedback, operation IDs, and the account's contact and reference identifiers. After success, briefly tell the user it was submitted. Report only issues Markifact itself caused. Low-level operations such as gads_mutate or meta_ads_update_adset pass requests straight to the platform, so their responses are the platform's, not Markifact's. A write the platform accepted is complete; if the state differs later, something else changed it. If you are unsure how a platform behaves, research its documentation. Never report third-party policies, outages, rate limits, rejected content, campaign performance, or user configuration. Before reporting a missing capability, use find_operations to check for a dedicated or generic operation that supports it. Never run a write just to test whether a capability exists. Include only the minimum non-sensitive evidence and summarize errors instead of copying raw data. Never include passwords, API keys, tokens or other auth details, payment information, raw conversation history, full request or response payloads, or unrelated personal or customer data. Avoid duplicate reports. Use `other` only when the feedback does not fit another category. Write the title and description in English. Do not promise that Markifact will respond or implement a fix. Returns JSON confirming whether the submission succeeded.
The description explains the capability, when to use it, and what to expect.
Inputs70/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
category
Feedback type: bug, feature_request, improvement, or other.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
title
Concise English title describing the Markifact issue, up to 140 characters.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
description
Concise English explanation of the expected behavior, actual behavior, user impact, and minimal non-sensitive evidence, up to 10,000 characters.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
impact
Severity based on blocked work and affected scope: low, medium, or high.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
operation_ids
Relevant Markifact operation IDs, when known.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
Annotations100/100
All four behavior hints are declared.
{
"title": "Report Markifact Feedback",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}Output schema31/100
Describe the returned fields so an agent can interpret the result.
View output schema
{
"type": "object",
"required": [
"result"
],
"properties": {
"result": {
"type": "string"
}
},
"x-fastmcp-wrap-result": true
}