Coming off a brutal start for Toronto Blue Jays pitcher Kevin Gausman on Friday, the latest news regarding his status ahead of the trade deadline has likely been revealed. As the Blue Jays take on the Chicago Cubs this weekend, this MLB insider offers insight into why Gausman is more than likely to stay with the team.
MLB.com’s Thomas Harrigan would write about the teams that have “coveted” pitchers that should be sellers ahead of the trade deadline, with the discussion centering around Toronto. However, Harrigan would discuss why the Blue Jays are “unlikely” to deal Gausman, partly due to the American League being weaker this season and “bunched together.”
“Several factors are working against teams hoping to find a needle-mover on the rental market. For one, the standings are extremely bunched together, and there’s little indication that is going to change over the next few weeks. Take the Blue Jays as an example,” Harrigan wrote.
“The reigning AL champions have had a disappointing season but are firmly in the AL Wild Card picture anyway,” Harrigan continued. “Even if they continue to tread water, it’s unlikely that they are going to drop down far enough to trade pending free agent Kevin Gausman.”
A look at Blue Jays’ Kevin Gausman
So far this season with the Blue Jays, Gausman has posted a 4.04 ERA, 89 strikeouts, and a 4-5 record in 16 games. In his last start against the Cubs on Friday, it was one to forget as he had seven earned runs to go along with three strikeouts, four walks, and seven hits allowed.
At any rate, it remains to be seen if Toronto will stay pat and not be a seller when the trade deadline comes around, or if Gausman will be on the trade block. There is no denying the disappointment that the Blue Jays have had this season after a season removed from making it all the way to the World Series, being one game away from beating the stacked Los Angeles Dodgers.
Toronto has a 37-39 record, which puts them third in the AL East.
The post Blue Jays rumors: Why Kevin Gausman trade is unlikely appeared first on ClutchPoints.
