mcp-api-integration-create-or-update-file-fails-with-content-encoding--56ea660a

THEN Update the function schema to accept content as an object with 'encoding' (e.g., 'base64') and 'content' (base64-encoded string). For backward compatibility, if a plain string is provided, auto-base64 encode it and set encoding to 'base64'. Then pass the structured object to GitHub's API.

// Current schema (fails):
"content": { "description": "Content of the file", "type": "string" }

// Required fix:
"content": {
  "oneOf": [
    { "type": "string", "description": "Plain text to auto-encode" },
    {
      "type": "object",
      "properties": {
        "encoding": { "type": "string", "enum": ["base64"] },
        "content": { "type": "string" }
      },
      "required": ["encoding", "content"]
    }
  ]
}